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-mergegit 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-merge)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/spec-merge"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/spec-merge/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/huginnindustries/codecartographer/spec-merge"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/spec-merge.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.00027 | $0.00261 |
| Opus 5 | $0.00014 | $0.00130 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
merge-confirmed-specifications 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 8d 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
Merge Confirmed Specifications
Produce findings/spec-merge/merged-spec.md using templates/merged-spec.md.
Read the product vision, proposal, and only the library entries identified as human-confirmed in the phase prompt. The runtime preflight has already verified that at least one proposal checkbox is [x]; do not broaden the selection yourself.
Merge by concept, not by original repository structure:
- normalize capabilities that use different names for the same behavior,
- preserve load-bearing invariants and externally observable acceptance behavior,
- distinguish reusable semantics from adapters and source-specific delivery surfaces,
- record each incompatibility in the conflict ledger,
- choose
adopt,adapt,defer, orrejectonly when the evidence supports it, - keep gaps against the vision visible rather than filling them with invented behavior.
Every load-bearing row must cite an exact library reference and version, such as team/router@v2, or an exact section of the vision. A merged claim without provenance is a validation failure.
Treat library entries as read-only. End with Coverage and limits and the validation table from the template.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 24 lines · 27 tokens per session scan A f2f91f353973
merge-confirmed-specifications is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (4 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 261 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 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.
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.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.