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 HuginnIndustries/CodeCartographer --skill spec-delta-applicationgit clone --depth 1 https://github.com/HuginnIndustries/CodeCartographerWrote 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/huginnindustries/codecartographer/spec-delta-application)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/spec-delta-application"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/spec-delta-application.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.1 | $0.00121 | $0.01918 |
| Opus 5 | $0.00060 | $0.00959 |
| Sonnet 5 | $0.00024 | $0.00384 |
| Haiku 4.5 | $0.00012 | $0.00192 |
Grade A, and why
apply-spec-deltas 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Spec Deltas
Use this skill when:
- The pipeline has produced a complete
findings/reimplementation-spec/reimplementation-spec.md(the spec iscompletein status.yaml). - A separate source has surfaced changes the spec should absorb. Common sources:
- Spike reports (
scratch/spikes/<spike-id>/<scenario>.md, written fromtemplates/spike-report.md, plus an optionalCONSOLIDATED-DELTA.mdwhen several scenarios merge). - Defect-scan re-runs that find corrections to spec text.
- Implementation discoveries that contradict spec assumptions (e.g., a wire format the spec misread).
- Maintainer rulings that close prior open questions.
- Spike reports (
This is a post-pipeline activity. current_phase stays complete. The spec is updated in place; no phase status changes.
Core posture: triage, do not rubber-stamp
The single rule of this skill: don't apply deltas verbatim without thinking. Every delta gets categorized, and only some get applied. Rubber-stamping a delta list produces an incorrect spec — the discipline is the value.
Triage every delta into one of four buckets:
| Bucket | Definition | Action |
|---|---|---|
| APPLY | Delta is a real correction or required addition; the spec is wrong without it. | Edit the spec body. Add a [revised per <source> §<delta-id>] marker at the changed section. Record in DELTAS-APPLIED.md. |
| CLARIFY | Delta proposes wording change; the spec's meaning is correct but the language is ambiguous. | Edit the spec wording (not the rule). Record in DELTAS-APPLIED.md as a clarification. |
| DEFER | Delta is a real improvement but not load-bearing for the next implementation step. | Add to BACKLOG.md with rationale and a back-reference (templates/backlog-project.md gives the entry shape). Do NOT edit the spec. |
| REJECT | Delta is wrong on close reading (premise was incorrect, scope was misread, the rule it proposes already exists, etc.). | Document in DELTAS-APPLIED.md with a one-line rationale. Do NOT edit the spec. |
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 · +2 lines e2e1138f274d
- 6d ago First seen · 103 lines · 121 tokens per session scan A 30aee0b4e9dc
apply-spec-deltas is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (4 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 1,918 once invoked, about $0.0006 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
proactive-analysis
Automatically run a tech-debt scan before opening a pull request, after large refactors, or when the user asks for a code review — surface actionable findings without being asked.
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.