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.
git clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/commands/widnyana/eyay-toolkits/cg-map)<a href="https://agentmods.dev/commands/widnyana/eyay-toolkits/cg-map"><img src="https://agentmods.dev/badge/commands/widnyana/eyay-toolkits/cg-map.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.00013 | $0.00606 |
| Opus 5 | $0.00006 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
cg-map 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 7d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map the Design Graph method onto: $ARGUMENTS
Produce a vocabulary mapping so the method's three channels (A, E, R) and its markers have concrete, idiomatic counterparts in the target stack. Output a mapping table followed by a small worked mini-graph in Graph Protocol format.
Mapping table (required rows)
| Protocol concept | Question to answer for the target stack |
|---|---|
| A — happy path | Where does the straight-line happy path live? (main fn, do-block, generator pipeline, SQL CTE chain…) |
| E — failure carrying | How are failures values vs control flow? (Result/Either, checked exceptions, error returns, panics+recover, throw at layer joins…) |
| ⟳ retry | Idiomatic retry: library, decorator, middleware, policy object? |
| ↯ escape | Idiomatic fallback: default value, cache read, alternative path? |
| ☠ die | What counts as a defect? (assert, panic, raise RuntimeError, process abort…) |
| R — dependencies | How are deps declared and provided? (constructor injection, traits, typeclasses, DI container, closure capture, context.Context…) |
| 🔒 boundary parse | Where do unknown→trusted conversions live? (schema lib, DTO layer, parsing constructors, guards…) |
| (1) (N) (T) | One-shot vs stream vs time-bounded: iterators, channels, observables, TTL caches… |
| ⛈ behavior layers | Middleware/decorator/aspect story of the stack |
| Scope | RAII, defer, context managers, try-with-resources, drop… |
| A/E structural split | How the stack separates happy path from failure join points (pipe, middleware stack, Result chain, try/catch at edges) |
| E layer scoping | How each layer translates inner errors into its own error type before handing off |
Rules
- Be concrete: name actual libraries, patterns, and syntax idioms of the stack.
- If the stack lacks a native counterpart for a concept, say so and name the closest convention (and its cost).
- After the table, render a mini Design Graph (PROBLEM → header tree → GRAPH → VERDICT only) for a small example task in this stack, using the mapped vocabulary — proving the mapping works end to end.
- This mapping is a companion artifact: once produced, refer to it in later
/cg-planand/cg-reviewruns in the same stack.
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.
- 7d ago First seen · 41 lines · 13 tokens per session scan A e6b7eb06d911
cg-map is a command published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 606 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 commands, from other repositories
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
prep
Prepare a pre-meeting briefing by reviewing all memory files and surfacing items that need discussion.
launch
Run W5 Product Launch. Full GTM launch sequence including readiness audit, launch messaging, ethics clearance, and staged rollout plan. Produces go/no-go decision and post-launch monitoring plan.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.