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/alinaqi/maggyWrote 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/alinaqi/maggy/icpg-why)<a href="https://agentmods.dev/commands/alinaqi/maggy/icpg-why"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/icpg-why/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/commands/alinaqi/maggy/icpg-why"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/icpg-why.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.00000 | $0.00356 |
| Opus 5 | $0.00000 | $0.00178 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
icpg-why 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 9d 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.
What it actually says
/icpg-why — Why Does This Code Exist?
Trace any symbol back to its creating ReasonNode — show the original goal, who wrote it, and whether it's still doing what it was made for.
Usage
/icpg-why <symbol-name>
Steps
1. Find the symbol
icpg query risk <symbol-name>
If not found, search more broadly:
icpg query context <likely-file-path>
2. Show the full trace
WHY: <symbol-name>
═══════════════════
Symbol: <type> <name> (<file-path>)
Signature: <signature>
Checksum: <checksum>
CREATING INTENT:
ID: <reason-id>
Goal: <goal>
Type: <decision_type>
Owner: <owner>
Status: <status>
Created: <date>
CONTRACTS:
PRE: <preconditions>
POST: <postconditions>
INV: <invariants>
MODIFICATION HISTORY:
1. <date> — <modifying-reason-goal> (by <owner>)
2. <date> — <modifying-reason-goal> (by <owner>)
DRIFT STATUS: {CLEAN | DRIFTED}
Dimensions: <drift-dimensions if any>
Severity: <score>
3. If no ReasonNode found
Symbol exists but has no iCPG tracking:
⚠ No ReasonNode found for <symbol-name>.
This code has no tracked intent — consider creating one:
icpg create "<inferred goal>" --scope <file>
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.
- 9d ago First seen · 66 lines · 0 tokens per session scan A 237777adcda9
icpg-why is a command published in the GitHub repository alinaqi/maggy (705 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 tokens. 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 commands, from other repositories
frappe-backend
Treat the task as Frappe backend work.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.