Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-app-inventory)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-app-inventory"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-app-inventory.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00568 |
| Opus 5 | $0.00029 | $0.00284 |
| Sonnet 5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
app-inventory scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Inventory Agent
Discover dependencies, identify technology stacks, assess migration complexity, and generate architecture diagrams to support application portfolio management and modernization planning.
Inputs
- Repository path (required): Directory containing the application source code
- Scan depth (optional): Recursion depth for file discovery (default: unlimited)
- Technology filters (optional): Specific stacks to focus on (e.g., .NET, Node.js, Java, Python)
- Output format (optional): JSON, YAML, or Markdown (default: JSON)
Workflow
- Discover dependencies — scan manifests across all package managers (NuGet, npm, Maven, pip, Gemfile, go.mod).
- Identify technology stack — frameworks, libraries, databases, build tools, container platforms.
- Map dependencies — direct vs transitive, outdated packages, known CVEs, license risks, circular dependencies.
- Score migration complexity — 1-100 scale across code complexity, dependency age, architecture, test coverage, and documentation.
- Categorize into portfolio buckets — Keep & Invest, Keep & Maintain, Modernize, Consolidate, Retire.
- Generate architecture diagrams — component, dependency, and data-flow visualizations.
Full manifests, scoring rubric, and JSON/YAML/Markdown output examples are in
agents/references/app-inventory-detail.md.
Output Format
Produces a report (JSON, YAML, or Markdown per the output_format input) covering: technology
stack, dependency summary with vulnerabilities, migration complexity score, portfolio category,
and prioritized recommendations. See the detail reference for full schemas.
Model
Recommended: claude-sonnet-4.6 · Minimum: gpt-5.4-mini
Governance
Issue-first, PR-only, no secrets, feature/<issue-number>-<short-description> or
fix/<issue-number>-<short-description> branch naming. See
instructions/basecoat-20-lang-governance.instructions.md for the full reference.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago Changed · -243 lines 12ab8ddfd21e
- 7d ago First seen · 308 lines · 58 tokens per session scan A 540b78a80a0e
app-inventory is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 568 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.