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/zaryab2000/decipher-gas-optimizoorWrote 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/zaryab2000/decipher-gas-optimizoor/watch)<a href="https://agentmods.dev/commands/zaryab2000/decipher-gas-optimizoor/watch"><img src="https://agentmods.dev/badge/commands/zaryab2000/decipher-gas-optimizoor/watch.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.00000 | $0.00644 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
watch 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/decipher-gas-optimizoor:watch
Toggle real-time gas annotation mode. When active, Claude appends a gas impact note after every Solidity edit it makes in the current session.
Activation
When the user runs /decipher-gas-optimizoor:watch (with no --off flag), output exactly:
Gas Watch Mode: ACTIVE — I will annotate every Solidity edit with a gas impact note.
No other output. No confirmation questions. Mode is immediately active.
Behavior while active
After every message in which Claude writes, edits, or rewrites Solidity code, append this annotation block at the end of the response — after describing the change but before any follow-up questions:
---
Gas note: [what changed and why it affects gas]
Estimated: [+/-X gas] per call to [function name or "all callers"]
Rules for the annotation:
- Be specific: name the opcode or pattern (SLOAD, SSTORE, calldata vs memory, unchecked, custom error, etc.).
- Include a numeric estimate. Use ranges when the exact saving depends on input size or call frequency (e.g., "~97 gas/warm SLOAD avoided × N iterations").
- If the change has no gas impact (e.g., a comment change or NatSpec addition), write:
Gas note: No gas impact — comment/NatSpec only. - If the change introduces a gas regression, flag it clearly:
Gas note: REGRESSION — [what got worse and why] Estimated: +X gas per call to [function name] - One annotation block per response, even if multiple files were edited. Summarize all edits in a single note; list separate line items if edits affect different functions.
Example annotation
Gas note: Replaced `require(msg.sender == owner, "Not owner")` with custom error
`NotOwner()` — eliminates ABI-encoded string revert data (4 bytes selector vs ~96 bytes
`Error(string)` encoding) and reduces deployment bytecode by ~200 bytes.
Estimated: -20 gas per call to setOwner() on the revert path; -~40,000 gas deployment.
Deactivation
When the user runs /decipher-gas-optimizoor:watch --off, output exactly:
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.
- 8d ago First seen · 74 lines · 0 tokens per session scan A 189ad5f36462
watch is a command published in the GitHub repository zaryab2000/decipher-gas-optimizoor (7 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 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-31.
Other commands, from other repositories
scaffold
Create a new Stellar dApp project from scratch using the framework templates.
deploy
Deploy Stellar contracts to a target network.
deploy
Deploy Solana program (devnet first, then mainnet).
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.