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 skills add Anuj7411/sipcode --skill sipcode-whygit clone --depth 1 https://github.com/Anuj7411/sipcodeWrote 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/anuj7411/sipcode/sipcode-why)<a href="https://agentmods.dev/skills/anuj7411/sipcode/sipcode-why"><img src="https://agentmods.dev/badge/skills/anuj7411/sipcode/sipcode-why/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anuj7411/sipcode/sipcode-why"><img src="https://agentmods.dev/badge/skills/anuj7411/sipcode/sipcode-why.svg" alt="Reviewed on agentmods" width="80" 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.00073 | $0.01255 |
| Opus 5.5 | $0.00029 | $0.00502 |
| Sonnet 5.5 | $0.00015 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
sipcode-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 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Why a Codex session was expensive
Answer from the user's own Codex logs on this computer, through the published sipcode command. Explicit instructions from the user take priority over this skill.
Run Sipcode
- Run the command for the question below straight away. Do not check the Sipcode version first: every extra command is another request that re-sends this whole chat. If the shell says
sipcodeis not found or not recognized, tell the user: "Sipcode is not installed. Runnpm i -g sipcodeonce in a terminal, then ask again." and stop. If Sipcode says the command or an option is unknown, tell the user: "Your Sipcode is older than this plugin. Runnpm i -g sipcode@latest, then ask again." and stop. Do not trynpx(the sandbox usually blocks network access) and do not install anything yourself. - Sipcode reads
~/.codex(or the folderCODEX_HOMEpoints to). If the sandbox blocks that folder (a permission error, or a result that says no sessions while the user clearly uses Codex), request permission to run the same command again with read access to that folder, for example by running it outside the sandbox. Do not report an empty result caused by the sandbox. - Never open, read, search or summarise the log files yourself, and never paste their contents. Work only from Sipcode's output.
Pick one command
| The user asks about | Run |
|---|---|
| the last (most recent) session | sipcode why --agent codex --json |
| a specific session | sipcode why --agent codex --list to find its id, then sipcode why --agent codex --session <id> --json |
The session you are in right now is also a Codex session: if the user means an earlier one, use --list and ask which one when it is not clear. Lines Sipcode prints on stderr that start with note: are part of the answer. If Sipcode prints a line starting "warning:" that log files could not be read, say it first in your answer, as printed: the numbers leave those logs out. With --json the same thing comes on stderr as a note: that log files or folders could not be read or parsed, or that compressed logs were skipped: say that first too.
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 Changed cc3295c709af
- 4d ago Changed · +12 lines 1a1386a9eaae
- 6d ago First seen · 32 lines · 73 tokens per session scan A 06b5f0aa9257
sipcode-why is a skill published in the GitHub repository Anuj7411/sipcode (46 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,255 once invoked, about $0.0003 per session on Opus 5.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-10-13.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…