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 instructions/dees91/agent-skill-manager/claude-mdgit clone --depth 1 https://github.com/dees91/agent-skill-managerWrote 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/instructions/dees91/agent-skill-manager/claude-md)<a href="https://agentmods.dev/instructions/dees91/agent-skill-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/dees91/agent-skill-manager/claude-md.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 | $0.00492 | $0.00492 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
agent-skill-manager CLAUDE.md 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
Claude Code Guidance
This repository uses AGENTS.md as the canonical project brief for all agents.
Before making code or documentation changes:
- Read AGENTS.md.
- Read docs/wiki/README.md and docs/wiki/index.md, then open the topic pages relevant to the task.
- If working on the MVP implementation, read planning/phase-1-mvp-tasks.md.
- If working on group or bulk toggle behavior, read planning/phase-2-group-bulk-toggle-tasks.md.
- If working on repository installation behavior or documentation, read planning/phase-3-repo-install-tasks.md.
- If working on repository update or uninstall behavior or documentation, read planning/phase-4-repo-update-uninstall-tasks.md.
- If working on local path install or uninstall behavior or documentation, read planning/phase-5-local-path-install-tasks.md.
- If working on the desktop app, read the relevant Phase 6-10 planning file.
- If working on publication or repository hygiene, read planning/phase-11-publication-readiness-tasks.md.
- If working on GitHub release artifacts, read planning/phase-12-github-release-tasks.md.
- Follow the task status rules in the relevant planning file before starting and after finishing work.
After non-trivial work that creates reusable knowledge, update the relevant wiki topic/source pages and append to docs/wiki/log.md. The wiki is a synthesis layer; verify current behavior against code and tests and keep accepted product decisions in AGENTS.md and the relevant planning file.
Do not implement behavior that contradicts the decisions recorded in AGENTS.md without first updating the plan with the user.
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 · 22 lines · 492 tokens per session scan A 43e50b76f35e
agent-skill-manager CLAUDE.md is an instructions file published in the GitHub repository dees91/agent-skill-manager (1 stars, last pushed 9d ago), licensed MIT. It adds 492 tokens to every session, about $0.0025 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 instructions, from other repositories
plinth AGENTS.md
AGENTS.md instructions for jabrena/plinth, covering contributor quickstart guide, your role, tech stack, framework version baseline and internal scripts.
claude-sports-analytics CLAUDE.md
Instructions for PuckAPI/claude-sports-analytics, covering hockey skills -- claude code instructions, public repo rules, never include, commit messages and code and content.
plinth CLAUDE.md
Claude Code instructions for jabrena/plinth, a project described as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.
DSPy-Programming-not-prompting-LMs-skills CLAUDE.md
Claude Code instructions for lebsral/DSPy-Programming-not-prompting-LMs-skills, covering dspy skills repository, conventions, workspace directory, repo structure and adding or updating a skill.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.