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 commands/gnayj/claude-code-sop/sop-tiergit clone --depth 1 https://github.com/Gnayj/claude-code-sopWrote 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/commands/gnayj/claude-code-sop/sop-tier)<a href="https://agentmods.dev/commands/gnayj/claude-code-sop/sop-tier"><img src="https://agentmods.dev/badge/commands/gnayj/claude-code-sop/sop-tier.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.00017 | $0.01112 |
| Opus 5 | $0.00009 | $0.00556 |
| Sonnet 5 | $0.00003 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
sop-tier 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sop-tier — inspect or set consumed model tiers
Work in ${CLAUDE_PROJECT_DIR}. This command is a thin UX wrapper over ccsop_configure. It
never edits TOML directly and never offers a shell/manual-edit fallback.
Step 0 — guards
Apply the orphaned-root and missing-config guards from /sop-flow. Discover
ccsop_configure; if the tool is missing/old/unregistered, make zero writes and direct the user
to /mcp plus reconnect/restart.
Call action=status. Require contract_version=2 and observed_schema=1|2. Schema absent means
/sop-update must run the fixed migration actions; an unknown schema/contract fails loud with zero
writes. Schema 1 preserves the four Phase 1 scopes below.
If status returns config_valid=false, show its validation_error and raw tier values. An
explicit legal set may repair the selected invalid tier key: the server publishes only when the
resulting whole config passes TOML+Zod validation. Unrelated invalid fields (or uninspectable
TOML) reject with zero writes; report the exact field and recover via /sop-update where
supported or a verified .ccsop/backups/config/<sha256>.toml preimage. Never hand-edit on behalf
of this command.
Step 1 — scopes and status
Expose only scopes with a real runtime consumer:
| Public command scope | Machine scope | Consumer |
|---|---|---|
claude |
claude-review |
[review.claude] |
review |
codex-review |
[review.codex] |
implement |
codex-dispatch |
existing [implement] Codex dispatcher |
default |
codex-default |
shared [codex] fallback |
claude-implement |
claude-implement |
schema-2 claude_implement proposal adapter |
The claude-implement row is available only when schema=2 and the live tool catalog contains
claude_implement; otherwise fail that scope with /sop-update + /mcp remediation while keeping
the four Phase 1 rows usable. The current host Claude or Codex session model is selected with the
host's built-in /model, not through this command.
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.
- 4d ago First seen · 92 lines · 17 tokens per session scan A 3aeae65c347c
sop-tier is a command published in the GitHub repository Gnayj/claude-code-sop (2 stars, last pushed 23d ago), licensed MIT. It adds 17 tokens to every session and 1,112 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.