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 commands/smrafiz/claude-supercharger/devloggit clone --depth 1 https://github.com/smrafiz/claude-superchargerWrote 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/smrafiz/claude-supercharger/devlog)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/devlog"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/devlog.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 | $0.00000 | $0.00303 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
devlog 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 4d 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
Add an entry to the project's DEV-LOG.md: $ARGUMENTS
DEV-LOG.md is a living architecture journal — a running log of non-obvious decisions, context that isn't in the code, and rationale that git commit messages can't hold. It is NOT a changelog. It captures the WHY.
Step 1 — Locate or create DEV-LOG.md
Check if DEV-LOG.md exists in the project root. If not, create it with a header:
# DEV-LOG
Running log of architectural decisions, non-obvious context, and rationale.
Most recent entries at the top.
Step 2 — Draft the entry Gather from context (current task, recent changes, conversation):
- What decision was made or what changed
- Why — the constraint, tradeoff, or rationale (this is the essential part)
- What was rejected and why (if applicable)
Step 3 — Write the entry
Format:
## YYYY-MM-DD — [short title: what this is about]
**What:** [1-2 sentences describing the decision or change]
**Why:** [the reason — constraint, incident, stakeholder requirement, tradeoff chosen]
**Rejected:** [what was considered but not chosen, and why — omit if nothing notable]
Prepend the new entry (most recent at top). Do not modify existing entries.
Step 4 — Confirm State the entry path and the title of the entry added.
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.
- 4d ago First seen · 37 lines · 0 tokens per session scan A f370ad59cfba
devlog is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.