Inventory

Developer AI tool inventory

A repository and tool inventory for Cursor, Copilot, AI agents, code-review assistants, CLIs, and extensions.

Use For

Make the template part of an approval workflow.

Copy it into your internal wiki, ticket system, or policy document. Replace bracketed placeholders before sharing it with employees or customers.

Template handling rules

Do not paste real secrets, customer records, or private keys into the template.
Assign an owner and review date before relying on it.
Use the linked guide when the decision needs more context.

Copyable Template

Developer AI tool inventory

Developer AI Tool Inventory

Owner: [Name]
Team: [Engineering team]
Last reviewed: [Date]

Tool inventory

| Tool | Users | Account type | Repositories allowed | Agent/terminal access | Data restrictions | Admin owner | Review date |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Cursor / Copilot / CLI / extension] | [Names or roles] | [Company/personal] | [Repos] | [None/read/edit/terminal] | [Restrictions] | [Name] | [Date] |

Repository approval levels

| Repository | Classification | AI access level | Required controls | Approved by | Review date |
| --- | --- | --- | --- | --- | --- |
| [Repo] | [Public/internal/product/restricted] | [Blocked/read/edit/terminal] | [Rules, CI, scan, review] | [Name] | [Date] |

Minimum controls
- Use company accounts for company code.
- Enable privacy and team controls where available.
- Remove production secrets and real customer data from local workspaces.
- Add repository AI rules and ignore files where supported.
- Keep code review, CI, dependency checks, and secret scanning mandatory.
- Require approval before AI agents run network, install, delete, deploy, or infrastructure commands.

Incident notes
- Exposed secret or customer data: [Date / action / owner]
- Tool removed or restricted: [Date / reason]
- Next review: [Date]