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 visibilitygit 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/visibility)<a href="https://agentmods.dev/skills/zaryab2000/decipher-gas-optimizoor/visibility"><img src="https://agentmods.dev/badge/skills/zaryab2000/decipher-gas-optimizoor/visibility/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/visibility"><img src="https://agentmods.dev/badge/skills/zaryab2000/decipher-gas-optimizoor/visibility.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.00088 | $0.01313 |
| Opus 5 | $0.00044 | $0.00656 |
| Sonnet 5 | $0.00018 | $0.00263 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
visibility 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Identify functions declared public that are never called internally and remove
manual getter functions that duplicate Solidity's auto-generated getters. Both
changes reduce unnecessary bytecode and enable downstream optimizations.
public functions generate two ABI dispatch entry points: one for external calls
(reads from calldata) and one for internal calls (parameters on stack/memory).
external eliminates the internal entry point, enabling calldata for reference
parameters.
When to Use This Skill
- Writing or reviewing any Solidity function declaration
- Code review of contracts with many
publicfunctions - Pre-audit cleanup of a Foundry-based Solidity project
- After adding new external entry points that do not call internal functions
- After applying VI-001: combine with CD-001 (calldata) for max impact
When NOT to Use This Skill
- Functions already declared
external— already optimal - Contracts with no
publicfunctions - Interface-only files or abstract contracts where visibility is inherited
- When only reviewing test files (visibility in tests has no gas impact)
- Functions called internally via bare name (
_fn()) orthis.fn()— must staypublic
Platform Detection
Trigger on any .sol file containing public function declarations or manual
view getter functions. No tooling prerequisites beyond Read.
# Find public functions
grep -n "public" src/**/*.sol | grep -v "^.*\/\/"
# Find manual getter candidates (view returns single value)
grep -n "view returns" src/**/*.sol
Quick Reference
| Situation | Action |
|---|---|
| Function called only externally? | Change to external (VI-001) |
| Function takes array/struct params AND is external? | Also use calldata (VI-001 + CD-001) |
Manual getter for a public state variable? |
Remove it (VI-002) |
Function called internally (same contract, no this.)? |
Must stay public or internal |
Function called via this.fn() from inside the contract? |
Must stay public |
Required by interface (e.g., ERC-20 balanceOf)? |
Keep with appropriate visibility |
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.
- 10d ago First seen · 150 lines · 88 tokens per session scan A da9daeb39add
visibility is a skill published in the GitHub repository zaryab2000/decipher-gas-optimizoor (7 stars, last pushed 6mo ago), licensed MIT. It adds 88 tokens to every session and 1,313 once invoked, about $0.0004 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.
flounder
Operates Flounder, an autonomous white-hat security auditor. Use when a user asks for a security audit, bug-bounty review, vulnerability investigation, or exploit proof for a public-source or authorized repository, source tree, package, smart contract, Solidity/EVM project, ZK or proof-system code, deployed address…
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.