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/demondamon/agenticx/code-module-summariesnpx skills add DemonDamon/AgenticX --skill code-module-summariesgit clone --depth 1 https://github.com/DemonDamon/AgenticXWhat 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.00041 | $0.03343 |
| Opus 5 | $0.00020 | $0.01672 |
| Sonnet 5 | $0.00008 | $0.00669 |
| Haiku 4.5 | $0.00004 | $0.00334 |
Grade A, and why
code-module-summaries 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 yesterday.
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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Module Summaries
Overview
Build and maintain evidence-backed Markdown summaries for an arbitrary Git repository. Treat each module's last successful commit SHA as its incremental checkpoint. Timestamps and Markdown mtimes are display metadata only.
The tracked control directory is the source of truth:
registry.json: stable module boundaries, layout, and summary paths.state/<module-id>.json: one independent checkpoint per module.modules/*.md: summaries when using the centralized layout.INDEX.md: links and module ownership; update only when mappings change.
Invocation
Interpret user arguments with this contract:
/code-module-summaries [repo]
[--output <control-dir>]
[--layout centralized|colocated|custom]
[--update]
[--module <id-or-exact-name>]...
[--target <git-ref>]
[--refresh-modules]
[--summary-name <filename.md>]
[--head-only]
[--accept-summary-drift]
[--adopt-existing-summary]
[--rebaseline --reason <text>]
Defaults:
repo: current Git root.--output:code-summaries/.--layout:centralized.--target: the registry'stracked_ref, normallyHEAD.--summary-name:MODULE_SUMMARY.mdfor colocated summaries.
--layout custom places each module's Markdown at an arbitrary in-repository
.md path declared per module in registry.json (summary_path), with no
fixed directory shape. This is the layout for a shared conclusions/-style
tree, for example enterprise/conclusions/apps/gateway_conclusion.md. A custom
registry may also declare a top-level index_path (e.g.
enterprise/conclusions/README.md): a managed overview file the agent
maintains, excluded from module source diffs and unassigned-path checks. See
REFERENCE.md §9 for exact rules. centralized and colocated
are unchanged.
--module is repeatable and case-sensitive. It selects exact IDs first, then
an exact unique name. Never use fuzzy matching for a write operation.
Required Reference and Helper
What ships with it
3 files 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.
- yesterday First seen · 329 lines · 41 tokens per session scan A 7cdebc666d69
code-module-summaries is a skill published in the GitHub repository DemonDamon/AgenticX (219 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 3,343 once invoked, about $0.0002 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-30.
Other skills, from other repositories
skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
update-setup
One-time setup wizard for the nanobot upgrade skill. Triggers: setup update, configure update, 设置更新, 初始化更新.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
cron
Schedule reminders and recurring tasks.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
weather
Get current weather and forecasts (no API key required).