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-regressgit 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-regress)<a href="https://agentmods.dev/skills/anuj7411/sipcode/sipcode-regress"><img src="https://agentmods.dev/badge/skills/anuj7411/sipcode/sipcode-regress/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-regress"><img src="https://agentmods.dev/badge/skills/anuj7411/sipcode/sipcode-regress.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.00105 | $0.01250 |
| Opus 5.5 | $0.00042 | $0.00500 |
| Sonnet 5.5 | $0.00021 | $0.00250 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
sipcode-regress 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 today.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Did Codex or Claude Code get worse after an update?
Answer "is it the tool or is it me?" from the user's own logs on this computer, through the published sipcode command, with evidence they can attach to a bug report. 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. -
If the user asks about Codex or does not name a tool, run the Codex check once:
sipcode regress --bug-report --agent codexIt reads only the Codex logs in
~/.codex(usually about a second) and compares each Codex version with the user's other versions.Run the Claude Code check only when the user explicitly asks about Claude Code:
sipcode regress --bug-report --agent claude-code, orsipcode regress --bug-report(no--agent) when they ask about both tools. It reads~/.claude/projects(and~/.codexfor both). Before running it, tell the user the first run can take a minute or more on large Claude Code logs. Give the command a timeout of at least 3 minutes. Use no other options.A run cut off by a timeout prints nothing, and empty output is never a result: if the command returns no output at all, run it again with a longer timeout before answering.
-
If the sandbox blocks a log folder (the output says "Not found or not readable", prints a WARNING that files could not be read, or the command exits with code 2), request permission to run the same command again with read access to those folders, for example by running it outside the sandbox. Do not report a result from a blocked run.
-
Never open, read, search or summarise the log files yourself, and never paste their contents. Work only from Sipcode's output.
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.
- today Changed · +5 lines d82332399b25
- yesterday Changed 24e650958a49
- 3d ago First seen · 41 lines · 105 tokens per session scan A 3abf12ae0a36
sipcode-regress is a skill published in the GitHub repository Anuj7411/sipcode (46 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 1,250 once invoked, about $0.0004 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
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
system-health
Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…
vc:debug
Debug systematically with root-cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, CI failures, or system investigation.
vc:chrome-devtools
Automate browsers with Puppeteer CLI scripts and persistent sessions. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, JavaScript debugging.
mac-deep-clean
Deep-clean a macOS dev machine — reclaim disk (caches, dev-tool caches, dead repos, git worktrees, Android/Xcode/simulator bloat, System Data) and diagnose/fix memory exhaustion (runaway process leaks, swap thrashing, wired RAM). Use when disk is full, "System Data" is huge, the machine is swapping/slow, or the user…
vc:sequential-thinking
Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.