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/anuj7411/sipcode/whynpx skills add Anuj7411/sipcode --skill whygit clone --depth 1 https://github.com/Anuj7411/sipcodeWhat 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.00090 | $0.00327 |
| Opus 5 | $0.00045 | $0.00163 |
| Sonnet 5 | $0.00018 | $0.00065 |
| Haiku 4.5 | $0.00009 | $0.00033 |
Grade A, and why
why 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.
What it actually says
Sipcode — Why (session forensics)
Call the sipcode:audit_latest_session MCP tool to produce a forensic report of the user's most recent Claude Code session.
If the user provides a session ID prefix (e.g., "audit session 3bca35e2"), pass it as the session_id argument. Otherwise, omit and the tool will pick the most recent session across all projects.
When presenting the result:
- Lead with the output ratio (the percentage of total tokens that were actual code output). 0.3–2% is typical.
- Surface the top 3 leaks with their dollar cost.
- The "Sipcode estimates ~X tokens were RECOVERABLE" line is potential, not realized. Only realized after
sipcode rules --install+ new sessions +sipcode impact. Be explicit about this when relaying the number. - If the session is unusually large (> $10) or unusually wasteful (output ratio < 0.2%), call that out.
Do NOT extrapolate the single-session savings across many sessions. Each session is its own forensic snapshot.
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 · 18 lines · 90 tokens per session scan A cbdf906dd563
why is a skill published in the GitHub repository Anuj7411/sipcode (46 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 327 once invoked, about $0.0005 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
audit-pr-architecture
Audit a PR's structural choices against architecture-priming, the repo's own architecture.md, and any nested boundary configs. Use when the user says "audit this PR's architecture", "check the boundaries", "is this PR clean structurally", "post-merge review of.
docs-voice
Voice, tone, and format for the public Codemap docs (apps/docs, built with Blume). Use when authoring or editing apps/docs prose — landing, guides, concepts, recipes, reference, generated API — or deciding headline grammar, benefit framing, peer framing, or anti-pitch wording.
improve-codebase-architecture
Find deepening opportunities in the codebase, informed by the domain language in docs/glossary.md and the architecture in docs/architecture.md. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
writing-agents-config
Codemap repo hybrid deltas for .agents/ — tiers, rule-skill pairing, repo exemplars. Use when creating or reviewing rules/skills in this repo. Read writing-great-skills first for skill vocabulary and authoring principles.
agents-tier-system
Full tier assignments, pairing conventions, and authoring checklist for .agents/ rules and skills. Use when creating or reviewing a rule or skill, deciding Tier 1 vs 2 vs 3, or auditing attachment cost.
verify-after-each-step
Per-file verification checklist — lint-staged and package.json scripts after each milestone.