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/espennilsen/pi/agents-md-managernpx skills add espennilsen/pi --skill agents-md-managergit clone --depth 1 https://github.com/espennilsen/piWrote 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/espennilsen/pi/agents-md-manager)<a href="https://agentmods.dev/skills/espennilsen/pi/agents-md-manager"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/agents-md-manager.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.00048 | $0.00864 |
| Opus 5 | $0.00024 | $0.00432 |
| Sonnet 5 | $0.00010 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
agents-md-manager 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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md Manager
Maintain AGENTS.md project context files across all ~/Dev projects.
Available Operations
1. Audit — Cross-project health check
Scan all projects and report AGENTS.md / .pi/ / td status:
# Use the project_init tool in batch mode
Use project_init with action: "batch" to get a full overview. Then provide a table:
| Project | Stack | AGENTS.md | .pi/ | td | Status |
|---|
Flag projects that:
- Have code but no AGENTS.md (needs init)
- Have AGENTS.md but no .pi/ or td (partially set up)
- Are fully ready ✅
2. Generate — Create AGENTS.md for a project
Use project_init with action: "detect" first to preview, then action: "init" to create.
After auto-generation, review and enhance the output by:
- Reading README.md for project description and purpose
- Checking package.json scripts for accurate quick-start commands
- Looking at src/ structure for meaningful directory descriptions
- Adding project-specific conventions found in configs (ESLint rules, Prettier settings)
- Adding deployment info if found (Dockerfile, CI workflows, deploy scripts)
3. Update — Refresh specific sections
When a project has changed significantly:
- Read current AGENTS.md
- Run
project_initwithaction: "detect"to get fresh stack profile - Compare detected state against documented state
- Update only stale sections, preserving manual edits in other sections
Key sections to check:
- Stack: Dependencies changed?
- Quick Start: New scripts added/removed?
- Directory Layout: New top-level dirs?
- Conventions: Linting/formatting tools changed?
- Key Files: New config files?
Use the edit tool for surgical updates — don't rewrite the entire file.
4. Sync Check — Detect drift
Compare AGENTS.md claims against reality:
# Check if referenced directories exist
# Verify scripts in package.json match what's documented
# Confirm referenced config files exist
# Check if new top-level dirs aren't documented
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.
- 6d ago First seen · 109 lines · 48 tokens per session scan A 5412283132fc
agents-md-manager is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 13d ago), licensed MIT. It adds 48 tokens to every session and 864 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…