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/huginnindustries/codecartographer/broadsidenpx skills add HuginnIndustries/CodeCartographer --skill broadsidegit 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/broadside)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/broadside"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/broadside.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 | $0.00052 | $0.01455 |
| Opus 5 | $0.00026 | $0.00727 |
| Sonnet 5 | $0.00010 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
broadside 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broad-Side
Broad-Side is CodeCartographer's batch reconnaissance pass. It fires six
analysis lenses — architecture, API surface, security, mechanical defect scan,
convention extraction, and porting — at the repository as single-turn prompts
over the OpenRouter Batch API (~50% of sync pricing, asynchronous, unattended),
then synthesizes one cross-lens report. Results live under
.codecarto/broadside/<run>/ alongside this file.
What Broad-Side findings are — and are not
Broad-Side findings are unverified scouting signals, not validated claims. Every lens is one shot: no cross-file traversal, no runtime verification, no builds, no tests, no follow-up questions. The batch model is cheap, not strong. Treat every finding as a lead with a file:line pointer that the interactive pipeline — or you — must confirm before it is a fact.
This is the division of labor: Broad-Side is cheap enough to run on any repo to decide where the expensive interactive run should spend its attention. It does not replace any phase; it tells phases where to look.
Reading a Broad-Side run
- Read
synthesis.mdfirst. It carries the executive summary, severity counts, the top cross-lens findings, and per-module risk levels. - Read
triage.mdfor the work order: each lead scored by impact × difficulty with a P0–P3 priority and an effort estimate. It is a starting point for re-verification, not a commitment — every item still needs confirmation against the source before work begins. - Read the per-lens files behind anything that matters to your current phase:
architecture-*.json→ the architecture phase's seed of prior knowledgeapi-*.json→ endpoints and data types (contracts/protocols phases)security-*.json→ auth, trust boundaries (defect-scan-semantic pass 5)defect-*.json→ mechanical defect leads (defect-scan-mechanical)conventions-*.json→ naming/idiom candidates for CONVENTIONS.mdporting-*.json→ platform coupling (porting phase)
run-meta.jsonrecords scope: which lenses ran, at what cost, with what coverage caps.
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.
- 3d ago First seen · 115 lines · 52 tokens per session scan A 793a9e593d7a
broadside is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (4 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 1,455 once invoked, about $0.0003 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
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.
ctf-pwn
Solve CTF binary exploitation challenges by discovering and exploiting memory corruption vulnerabilities to read flags. Use for buffer overflows, format strings, heap exploits, ROP challenges, or any pwn/exploitation task.
deep-analysis
Performs focused, depth-first investigation of specific reverse engineering questions through iterative analysis and database improvement. Answers questions like "What does this function do?", "Does this use crypto?", "What's the C2 address?", "Fix types in this function". Makes incremental improvements (renaming…
ctf-rev
Solve CTF reverse engineering challenges using systematic analysis to find flags, keys, or passwords. Use for crackmes, binary bombs, key validators, obfuscated code, algorithm recovery, or any challenge requiring program comprehension to extract hidden information.
pyghidra-scripting
Write and run Python (PyGhidra) code inside the Ghidra session that ReVa's MCP server is already attached to, using the five ReVa scripting tools — run-script, list-scripts, read-script, write-script, edit-script. Use this whenever the user asks to execute Python against the current program, reach for the Ghidra Flat…
ctf-crypto
Solve CTF cryptography challenges by identifying, analyzing, and exploiting weak crypto implementations in binaries to extract keys or decrypt data. Use for custom ciphers, weak crypto, key extraction, or algorithm identification.