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 agentmods add instructions/biulight/shine/claude-mdgit clone --depth 1 https://github.com/biulight/shineWrote 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/instructions/biulight/shine/claude-md)<a href="https://agentmods.dev/instructions/biulight/shine/claude-md"><img src="https://agentmods.dev/badge/instructions/biulight/shine/claude-md.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 | $0.00011 | $0.00011 |
| Opus 5 | $0.00005 | $0.00005 |
| Sonnet 5 | $0.00002 | $0.00002 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
shine CLAUDE.md 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.
This is a copy
100% identical to datahub CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLAUDE.md
@AGENTS.md
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 · 4 lines · 11 tokens per session scan A 573138e19d33
shine CLAUDE.md is an instructions file published in the GitHub repository biulight/shine (5 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to datahub CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
chroma AGENTS.md
AGENTS.md instructions for chroma-core/chroma: See CLAUDE.md for codebase conventions (commit message format, etc.).
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.