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 aeonfun/aeon --skill rightstackgit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/rightstack)<a href="https://agentmods.dev/skills/aeonfun/aeon/rightstack"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/rightstack.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01041 |
| Opus 5 | $0.00022 | $0.00521 |
| Sonnet 5 | $0.00009 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
rightstack 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rightstack — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} - one RightStack query. Grammar:
<build goal>orrecommend: <build goal>- recommend a Web3 stack.workflow: <workflow-id>- inspect a known workflow.compare: <tool-a> | <tool-b>- compare two tools.explain: <tool-or-package>- inspect one tool.migrate: <package>- check a package migration path.- empty input - print the grammar and exit
RIGHTSTACK_EMPTY.
Today is ${today}. Use RightStack to produce a decision-ready Web3 architecture brief. RightStack is evidence to evaluate, not an authority: its corpus can be stale, incomplete, or route a broad prompt to the wrong workflow.
Integration boundary
This integration pins [email protected], which provides deterministic, versioned JSON for recommend, workflow, and compare. Treat schema_version: "1.0" as their contract boundary. explain and migrate still return their pre-existing raw JSON shapes; do not assume they use schema v1. Never scrape presentation-formatted terminal output.
The skill is advisory only. It does not install a recommended SDK, edit application code, create a wallet, deploy a contract, or submit a transaction. Those actions belong in a separate build skill after review.
Steps
- Read
memory/MEMORY.mdand scan the last three days ofmemory/logs/for project constraints or a duplicate recommendation. - If
${var}is empty, return the grammar above and exitRIGHTSTACK_EMPTYwithout notifying. - Run
node skills/rightstack/run.mjs. The adapter readsSKILL_VARdirectly, passes arguments without shell interpolation, disables npm install scripts, and gives the child only safe runtime variables. - Treat a non-zero exit as evidence. Report the operation, exit code, and concise stderr. Do not silently switch operations or invent a recommendation. Exit
RIGHTSTACK_TOOL_ERROR. - For
recommend,workflow, andcompare, confirmschema_version: "1.0"and the expectedcommand. Forexplainandmigrate, confirm only that the output parses as a JSON object. Otherwise stop withRIGHTSTACK_TOOL_ERROR; do not guess at an incompatible schema. - Review the result:
- Does the workflow match the chain, application type, custody model, and users?
- Are required and optional layers distinguished?
- Are named packages current enough to verify before implementation?
- Are security, vendor-lock-in, operational, and migration tradeoffs stated?
- Does it confuse a product migration with a package migration?
- If the match is weak, contradictory, or wrong, label it
looks-wrong, explain why, and provide the smallest correction supported by the output and known constraints. - Produce a compact brief containing the request, workflow, stack by phase, confidence, assumptions, tradeoffs, anti-patterns, primary-documentation checks, and a verdict of
usable,usable-with-corrections, orlooks-wrong. - Send the same substantive brief via
./notify -f <path>when useful. Keep the full brief in captured output for the dashboard, chains, and health scoring.
What ships with it
1 file 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.
- 3d ago First seen · 72 lines · 43 tokens per session scan A 8e2fbb568f0d
rightstack is a skill published in the GitHub repository aeonfun/aeon (716 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,041 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and flash loans. Use when building decentralized finance applications or smart contract protocols.
solidity-security
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
flowcraft-config
Author, validate, and troubleshoot complete FlowCraft deployment configuration (deploy.yaml with the runtime section, inference/workspace/sandbox/tool sub-documents, core/memory contracts, and graph JSON node wiring). Use when writing or reviewing FlowCraft configs, assembling an agent deployment, adding…
blockchain-web3
Solidity smart contracts, Web3 development, DeFi protocols, NFTs, EVM chains, Hardhat/Foundry tooling, and blockchain security. Use when writing smart contracts, building dApps, auditing contract security, or integrating Web3 wallets.