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/agents/zaryab2000/decipher-gas-optimizoor/gas-optimizer)<a href="https://agentmods.dev/agents/zaryab2000/decipher-gas-optimizoor/gas-optimizer"><img src="https://agentmods.dev/badge/agents/zaryab2000/decipher-gas-optimizoor/gas-optimizer.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.00095 | $0.00351 |
| Opus 5 | $0.00048 | $0.00176 |
| Sonnet 5 | $0.00019 | $0.00070 |
| Haiku 4.5 | $0.00010 | $0.00035 |
Grade A, and why
gas-optimizer 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.
What it actually says
Purpose
Conducts a comprehensive, multi-file gas optimization audit of a Foundry-based Solidity codebase. Produces a prioritized findings report with concrete code changes.
When to Use
- Full codebase audit before mainnet deployment
- Pre-audit gas optimization pass
- Optimizing an inherited codebase you did not write
Workflow
- Run /decipher-gas-optimizoor:baseline --update to establish current baseline
- Run forge inspect on every contract in src/ for storage layouts
- Apply all 11 skill domains systematically to each contract file
- Deduplicate findings across files
- Sort all findings by estimated gas saving (highest first)
- Produce the full /decipher-gas-optimizoor:analyze report format for the entire codebase
- Propose a commit sequence: "Fix these 3 first (highest impact, lowest risk)"
Scope
- Covers all 11 skill domains
- Works across multiple contract files
- Does not modify contracts — reports findings only
- Developer implements changes; hook guards against regressions
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 · 39 lines · 95 tokens per session scan A 4bc10696aa5b
gas-optimizer is an agent published in the GitHub repository zaryab2000/decipher-gas-optimizoor (7 stars, last pushed 6mo ago), licensed MIT. It adds 95 tokens to every session and 351 once invoked, about $0.0005 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 agents, from other repositories
security-reviewer
Review Solidity contracts for security vulnerabilities, incentive design, and OpenZeppelin best practices.
stellar-backend
Express API servers, indexers, and RPC services for Stellar.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
stellar-frontend
Next.js dApp UI with Stellar Wallets Kit and Stellar Agentic Kit hooks.
stellar-payments
You are a payments engineer specialized in Stellar agentic payment protocols. You implement x402 (HTTP 402 paid APIs via OZ Channels) and MPP (Machine Payments Protocol) in both Charge and Channel modes using USDC (SEP-41 SAC).
stellar-zk
Zero-knowledge proofs on Stellar — Groth16, Circom, Noir verifier contracts.