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 ShurikenTrade/shuriken-skills --skill scopinggit clone --depth 1 https://github.com/ShurikenTrade/shuriken-skillsWrote 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/shurikentrade/shuriken-skills/scoping)<a href="https://agentmods.dev/skills/shurikentrade/shuriken-skills/scoping"><img src="https://agentmods.dev/badge/skills/shurikentrade/shuriken-skills/scoping/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/shurikentrade/shuriken-skills/scoping"><img src="https://agentmods.dev/badge/skills/shurikentrade/shuriken-skills/scoping.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.00032 | $0.00695 |
| Opus 5 | $0.00016 | $0.00347 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
scoping 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scoping an agent key
Every agent key carries a set of scopes. A scope is a capability grant — read tokens, execute trades, read positions, deliver notifications. The server enforces scopes on every tool call and API endpoint; a call outside the granted scope fails with a structured authorization error.
Best practice: grant the minimum scopes the agent key actually needs
This is the single most important rule for agent-key scoping. For every agent key, grant only the scopes the integration actively uses — nothing speculative, nothing "just in case," nothing broader than the job requires.
Concretely:
- Start from what the integration does on its hot path, and enumerate only those capabilities.
- When in doubt, grant less and widen later if the integration errors on a missing scope.
- Create a separate agent key per integration (or per purpose) rather than one fat key reused everywhere — that way each key's scope surface stays tight.
- If a scope is required for a one-off setup step but not for steady-state operation, consider doing the setup with a broader key and then running with a narrower one.
Broader scopes are a liability: a leaked key is only as dangerous as the capabilities it carries.
Principles
- Separate read from write. Read scopes are generally safe; write/execute scopes move money or send messages and deserve more scrutiny.
- Per-integration, not per-user-role. A scope is a capability, not a persona. Reason about what the integration does, not who the user is.
Scope categories
Authoritative scope names live in the docs; these are the categories to reason about:
- Read scopes — querying token info, positions, wallet balances, alpha signals. Safe for analytics and display use cases.
- Trading scopes — planning trades, executing trades, cancelling orders. Required for any integration that moves funds.
- Delivery scopes — sending notifications (Telegram, email) on behalf of the user. Rate-limited.
- Administrative scopes — managing the user's agent keys themselves, linked wallets, etc. Typically not needed by third-party integrations.
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.
- 11d ago First seen · 56 lines · 32 tokens per session scan A edb871d57c07
scoping is a skill published in the GitHub repository ShurikenTrade/shuriken-skills (90 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 695 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-08-30.
Other skills, from other repositories
gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
recipe-create-classroom-course
Create a Google Classroom course and invite students.
smart-contract-reading-guide
How to read and understand smart contracts — navigating Etherscan, reading Solidity code, understanding ABIs, decoding transactions, and spotting common patterns. Use when helping users verify contracts, understand DeFi protocol mechanics, or decode on-chain activity.
wave
The starter skill. One tool, ten lines of handler: it plays the built-in wave gesture, then speaks a greeting. Referenced by examples/coach-leo/manifest.json and walked through in the skills guide.
web3-glossary
Comprehensive Web3 and DeFi glossary — definitions for 150+ terms covering blockchain, DeFi, NFTs, DAOs, L2s, and crypto culture. Use when a user asks what a term means or needs jargon explained in plain language.
rootdata-crypto-plugin
RootData is a leading Web3 data platform covering crypto projects, investors, funding data, and personnel movements. This skill is the OKX-dedicated integration, isolated from the standard RootData skill with its own API key namespace and endpoints.