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 broadside-scoutgit 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-scout)<a href="https://agentmods.dev/skills/huginnindustries/codecartographer/broadside-scout"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/broadside-scout/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/broadside-scout"><img src="https://agentmods.dev/badge/skills/huginnindustries/codecartographer/broadside-scout.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.00053 | $0.01073 |
| Opus 5.5 | $0.00021 | $0.00429 |
| Sonnet 5.5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
broadside-scout 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broad-Side Scout
This phase turns a Broad-Side batch reconnaissance run into a routing brief: a short document that tells each later phase where to spend its attention first. It runs before architecture, and everything downstream reads it.
The source code to analyze is in the parent directory (../ relative to
.codecarto/).
This phase spends no money
Broad-Side itself is fired by /codecarto-broadside submit (Pi) or
codecarto_broadside (MCP), and it is priced and confirmed there. This phase
only reads what those already wrote under broadside/<run>/. It never submits
a batch, and it must never instruct anyone to.
If no run exists, that is a legitimate outcome — see "When there is no run."
What you are reading, and what it is worth
Broad-Side findings are unverified scouting signals produced by a cheap batch model in a single shot: no cross-file traversal, no runtime verification, no builds, no tests, no follow-up questions.
The entire value of this phase is routing attention. The entire risk is that a lead gets copied forward as a fact. So the brief you write is a list of places to look, each addressed to a phase, and every entry carries the source pointer that phase must confirm for itself.
Nothing you write here is evidence. No later phase may cite this brief, or any
file under broadside/, as a source for a finding. A later phase cites the
code it confirmed.
Reading the run
- Find the most recent run directory under
broadside/. If several exist, use the newest and say which one you used. broadside/<run>/synthesis.md— the executive summary, severity counts, top cross-lens findings, per-module risk. Start here.broadside/<run>/triage.md— the same findings scored by impact × difficulty into a P0–P3 order with effort estimates.broadside/<run>/run-meta.json— which lenses ran, at what cost, with what coverage caps. This is where you learn what was not scanned.- The per-lens files only when a lead matters enough to need its detail.
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.
- 1mo ago First seen · 102 lines · 53 tokens per session scan A 40f5201c173d
broadside-scout is a skill published in the GitHub repository HuginnIndustries/CodeCartographer (6 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 1,073 once invoked, about $0.0002 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-09-07.
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.
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
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.
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.
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…
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…