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/stainless-code/codemap/agents-tier-systemnpx skills add stainless-code/codemap --skill agents-tier-systemgit clone --depth 1 https://github.com/stainless-code/codemapWhat 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.00049 | $0.01226 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
agents-tier-system 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.agents/ tier system — full reference
Always-on priming: .agents/rules/agents-tier-system.md. Entry points: .agents/README.md (hub), AGENTS.md (cross-tool stub), agents-first-convention, writing-agents-config.
Discover on disk (do not maintain partial catalogs here)
| Tier | How to list |
|---|---|
| Tier 1 | Frontmatter audit in agents-tier-system rule — budget set there |
| Tier 2 | ls .agents/rules/*.md + globs: in frontmatter |
| Tier 3 | alwaysApply: false, no globs: — intent via description |
| Skills | ls .agents/skills — runtime discovery via descriptions |
Pairing examples in this repo: consumer-surfaces (Tier 1, always-on); docs-governance (Tier 2 globs) ↔ docs-governance + docs-lifecycle-sweep; architecture-priming ↔ improve-codebase-architecture + audit-pr-architecture; agents-tier-system rule + skill; authoring-discipline rule + PROSE.md; verify-after-each-step rule + skill; codemap (skill-only); harden-pr (skill-only).
Caution: avoid stacking broad globs without thin priming bodies.
Authoring guidelines
Adding a new rule
- Decide the tier before writing.
- Tier 1 needs justification — every turn? If file/intent scoped, demote to Tier 2 or Tier 3.
- Tier 2 globs — broadest meaningful scope; pair with skill when applicable.
- Layout per
agents-first-convention— rules: source +.mdcsymlink; skills:.agents/only.
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.
- 2d ago First seen · 67 lines · 49 tokens per session scan A 77ab81e73d24
agents-tier-system is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 1,226 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-31.
Other skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
self-repair-pipeline
Runs the full entry point self-repair pipeline. Detects entry points in Ariadne packages or external codebases, triages false positives via sub-agents, plans fixes for each issue group with competing proposals and multi-angle review, and creates backlog tasks.
m1nd-guardian
Use when continuing, coordinating, reviewing, or handing off the M1ND-10 program; protecting its candidate tree; advancing G0-G10; freezing or releasing a candidate; activating autonomy; or when the user asks an agent to act as M1ND guardian. Enforces one-active-front execution, proof-state separation, same-candidate…
ctxo-understand
Use at the START of any code task (fix, extend, refactor, understand) before reading source files, to orient with ctxo and avoid going in the wrong direction.
agent-system-maintainer
Use this skill when modifying AI agents, skills, prompts, commands, hooks, instructions, MCP configuration, or platform-specific AI customization files.
reposkein-graph-rag
Navigates the local RepoSkein Code Property Graph to understand repository architecture. Use whenever modifying code, tracing dependencies, assessing change impact, or summarizing functions in a repo containing .reposkein/.