Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflownpx agentmods add skills/aimeerrhythm/enterprise-change-workflow/knowledge-repomapWrote 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/aimeerrhythm/enterprise-change-workflow/knowledge-repomap)<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/knowledge-repomap"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/knowledge-repomap.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.00028 | $0.00700 |
| Opus 5 | $0.00014 | $0.00350 |
| Sonnet 5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
knowledge-repomap 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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Structure Index Generator (Repo Map)
You are a code structure indexing tool. When user invokes this Skill, automatically scan project code and generate a structured index of class names and method signatures.
Prerequisites
Check if .claude/ecw/ecw.yml exists:
- Exists → Read
component_types,project.name - Not exists → Prompt user to run
/ecw-initfirst
Generation Steps
Step 1: Read Configuration
Extract from ecw.yml:
component_types[]— Component types to scan (name, grep_pattern, search_path)- Output file:
.claude/ecw/knowledge-ops/repo-map.md(fixed convention) project.name— Project name (for title)
Step 2: Run Generation Script
Based on project.language:
Java projects:
bash scripts/java/generate-repo-map.sh <project_root> <ecw_yml_path>
The script will:
- Extract component types from
component_types - Find matching files under corresponding
search_path - Extract class names and public method signatures
- Group output by subdirectory
- Write to
.claude/ecw/knowledge-ops/repo-map.md
Other languages:
- Currently Java only
- Prompt user: Repo Map generation not yet supported for this language, create manually or contribute a script
Step 3: Verify Output
Read the generated repo-map file, check:
- File was created successfully
- Total class count is reasonable (> 0)
- Each component type has matching results
Step 4: Output Summary
## Repo Map Generation Complete
- Output path: `.claude/ecw/knowledge-ops/repo-map.md`
- Scanned component types: <component_types list>
- Total: X classes
- Grouping: <by directory / flat>
The generated Repo Map can be used for:
1. Quick code entry point location (Facade, Controller)
2. Understanding overall project structure
3. Supplementary navigation alongside knowledge base
Suggestions:
- Run `/ecw:knowledge-repomap` to refresh after code structure changes
- Can be integrated into CI/CD pipeline for automatic generation
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.
- 6d ago First seen · 99 lines · 28 tokens per session scan A 77cff22fca54
knowledge-repomap is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 700 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
g-review
Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.
g-audit
Full-codebase or targeted code quality audit. Detects SOLID violations, code smells, architectural drift, dead code, and test coverage gaps. Targeted scope produces an inline report. Whole-codebase scope produces a prioritised roadmap milestone.
g-refactor
Guided refactor workflow — identify target, pre-analyse, spec, approve, execute, review. Accepts a scope path, an audit milestone file, or runs interactively. Safe-by-default: checks test coverage before execution and runs the full review gate after.
g-blast-radius
Analyse the blast radius of a planned change. Inputs a file path, feature name, or list of paths from a plan. Outputs the set of dependent files (forward and reverse references), a per-file volatility score (commit frequency proxy), and a total blast-radius rating (low / moderate / wide). Read-only.
cross-verify
A cross-checking skill that reviews decisions, designs, documents, and implementations from four viewpoints.
decompose
Break a large goal into 3–8 sequenced tasks, each one /eng → /tdd cycle. Writes to specs/{slug}.todos.md when a spec exists, root TODOS.md otherwise. /decompose — decompose a feature or goal /decompose re-entry — resume where you left off (auto-detected).