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.
npx agentmods add skills/ivegamsft/basecoat/app-inventorynpx skills add ivegamsft/basecoat --skill app-inventorygit 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/skills/ivegamsft/basecoat/app-inventory)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/app-inventory"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/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.00078 | $0.00275 |
| Opus 5 | $0.00039 | $0.00138 |
| Sonnet 5 | $0.00016 | $0.00055 |
| Haiku 4.5 | $0.00008 | $0.00028 |
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.
What it actually says
App Inventory Skill
Reusable templates and workflows for inventorying legacy application portfolios — producing audit-ready output for migration planning and sprint estimation.
Reference Files
| File | Contents |
|---|---|
references/workflow-guide.md |
5-step inventory workflow, downstream agent routing, related assets |
Templates in This Skill
| File | Purpose |
|---|---|
inventory-report-template.md |
Markdown report for architecture reviews and stakeholders |
complexity-scoring-template.md |
Scoring worksheet to derive migration complexity score |
Paired Agent
agents/basecoat-10-core-app-inventory.agent.md — see docs/treatment-matrix.md for app disposition decisions.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 35 lines · 78 tokens per session scan A a69e2c489e5f
app-inventory is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 275 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
tasklist
Maintain a project's canonical TASKS.md or an opted-in studio portfolio task register with permanent IDs, ownership, lifecycle dates, and source provenance. Use to list, add, update, complete, or cancel tasks, view tasks across registered projects, or import selected action items from project artifacts. Do not use for…
timetracker
Reconstruct daily or weekly project work from dated plans, decisions, meetings, site reports, tasks, and other artifacts, then append user-confirmed manual entries to TIMELOG.md. Use for "log my time," "what did I work on," daily timesheets, or weekly time reconstruction. Never infer hours, start/stop times, billing…
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…
project
Create or maintain an Architecture Studio project — initialize its record bundle, remember sourced facts, capture or supersede decisions, inspect project status, or migrate a 1.x PROJECT.md. Use when the user says “set up the project,” “remember this,” “we decided,” asks about project context, or runs /as:project.
site-visit-report
Create a typed, source-linked site visit report from field notes, photos, files, or conversation. Use for site observations, field reports, walkthrough records, existing-condition visits, and follow-up capture. Separate direct observations, participant-reported information, interpretation, limitations, issues, and…