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 skills add zaryab2000/decipher-gas-optimizoor --skill event-logginggit 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/skills/zaryab2000/decipher-gas-optimizoor/event-logging)<a href="https://agentmods.dev/skills/zaryab2000/decipher-gas-optimizoor/event-logging"><img src="https://agentmods.dev/badge/skills/zaryab2000/decipher-gas-optimizoor/event-logging/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/skills/zaryab2000/decipher-gas-optimizoor/event-logging"><img src="https://agentmods.dev/badge/skills/zaryab2000/decipher-gas-optimizoor/event-logging.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.00097 | $0.01619 |
| Opus 5 | $0.00048 | $0.00809 |
| Sonnet 5 | $0.00019 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
event-logging 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Identify storage arrays used solely for off-chain historical data and replace
the writes with event emission. Also audit event declarations for missing
indexed parameters on fields that callers will filter by.
When to Use
- Writing or reviewing functions that push to storage arrays
- Adding new events to a contract
- Pre-audit review of data retention patterns
- Reviewing any contract that stores audit trails, price history, or action logs
When NOT to Use
- When storage data must be read by on-chain code (another contract or the same contract reads the array on-chain)
- When historical data must survive contract replacement and be directly
accessible via
eth_getStorageAtwithout indexer infrastructure - When reviewing contracts with no storage arrays and no events
Rationalizations to Reject
| Rationalization | Why It's Wrong | Required Action |
|---|---|---|
| "We might need to read this on-chain later" | Speculation is not a reason to pay 22,100 gas per push today; if on-chain read is genuinely needed, design for it explicitly | Confirm on-chain read requirement before keeping storage |
| "Events can be lost or missed" | Events are part of the transaction receipt, permanent on-chain once included; off-chain indexers (The Graph, Etherscan) reliably capture them | Use events for historical data; storage only for current state |
| "It's just one array" | One array pushed once per user action at 1,000 users/day = 22,100,000 gas/day wasted | Estimate the volume, not the per-instance cost |
| "Removing storage might break existing callers" | Before removing, verify no external contract reads the array via eth_getStorageAt or ABI calls; confirm off-chain-only access |
Audit callers, don't assume |
Platform Detection
Trigger on any .sol file containing storage array push() calls or event
declarations without indexed parameters on address/uint256/bytes32 fields.
Quick Reference
| Data type | On-chain access needed? | Recommendation |
|---|---|---|
| Historical array pushes | No (only off-chain) | Replace with emit Event() |
| Current state value | Yes | Keep in storage |
Event address/uint256/bytes32 fields used for filtering |
— | Add indexed |
| More than 3 filterable fields | — | Index the 3 most important |
string/bytes event field |
— | Do NOT index (hashes value, loses original) |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 164 lines · 97 tokens per session scan A 33670ffe245c
event-logging is a skill published in the GitHub repository zaryab2000/decipher-gas-optimizoor (7 stars, last pushed 6mo ago), licensed MIT. It adds 97 tokens to every session and 1,619 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 skills, from other repositories
solidity-gas-optimizer
Analyze and optimize gas consumption in Solidity smart contracts using proven patterns and best practices.
blockchain-expert
Expert-level blockchain, Web3, smart contracts, DeFi, and cryptocurrency development. Use when the user mentions Web3, smart contracts, DeFi, Ethereum, or Solidity, or when the task involves Blockchain Fundamentals, Web3 & DeFi, Smart Contract Security, or Gas Optimization.
blockchain-application
Use this skill when asked about smart contract development, Solidity, Vyper, Rust smart contracts (Solana, NEAR, Polkadot), Haskell/Plutus (Cardano), Cairo/StarkNet, dApp backend development, Truffle, Hardhat, Foundry, Anchor, and blockchain application patterns. Languages: Solidity, Vyper, Rust, Haskell, Cairo, Move.…
web3-expert
Build production-ready Web3 applications including smart contracts, dApps, DeFi protocols, and decentralized storage solutions. Use when the user mentions Web3, smart contracts or Solidity, dApps, DeFi protocols, ethers.js or web3.js, IPFS, or on-chain integration with Ethereum-compatible networks.
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
pentagonal-clawd
Use when the user asks to create, generate, build, audit, fix, compile, or look up smart contracts and tokens. Pentagonal Clawd is a sovereign smart contract forge and token intelligence platform with AI-powered 8-agent security pen testing across Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, and BSC.