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/gcwing/bitfun/agents-mdgit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.05169 | $0.05169 |
| Opus 5 | $0.02584 | $0.02584 |
| Sonnet 5 | $0.01034 | $0.01034 |
| Haiku 4.5 | $0.00517 | $0.00517 |
Grade A, and why
BitFun AGENTS.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 2d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[中文](AGENTS-CN.md) | **English**
# AGENTS.md
BitFun is a Rust workspace plus React frontends.
Repository rule: **keep product logic platform-agnostic, then expose it through platform adapters**.
## Quick start
1. Read `README.md` and `CONTRIBUTING.md` before architecture-sensitive changes.
2. Use the primary product loop below for normal development. Surface-specific
alternatives belong in the nearest app guide.
3. After Rust file changes, prefer `pnpm run fmt:rs` to format only changed or staged `.rs` files. Use `cargo fmt` only when you intentionally want broader formatting coverage.
4. After changes, use the nearest local `AGENTS.md` for the focused verification
command. The repository-level verification section below only covers
cross-cutting checks.
5. Workspace Rust dependencies own compatible versions, not broad capability
unions. Each crate must select the dependency features it actually uses;
keep test-only features in dev-dependencies and attach feature-gated service
capabilities to the owning crate feature. Disable third-party defaults in
`[workspace.dependencies]` when they are not part of every consumer's
contract; members inherit that policy and add only their needed slices. For
internal crates whose guarded `default` is empty, do not repeat
`default-features = false` on every edge. Narrow consumers of an intentional
compatibility default, such as ACP, must still disable it explicitly.
Manifests copied into a standalone Docker build context must keep explicit
versions and default policy because they cannot inherit the workspace root.
`tokio/full` is forbidden in the root workspace and workspace members.
## Layered Module Index
Dependencies flow top to bottom. This table is the physical crate layout, not
the full conceptual architecture. For Product Surface / Product Assembly /
Product Feature / Agent Kernel / Execution / Extension / Cross-platform Adapter /
Stable Contracts and Security Control Plane bouWhat 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.
- 2d ago First seen · 371 lines · 5,169 tokens per session scan A 7e9b785a5d5d
BitFun AGENTS.md is an instructions file published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 2d ago), licensed MIT. It adds 5,169 tokens to every session, about $0.0258 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 instructions, from other repositories
serena copilot-instructions.md
Instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!
serena AGENTS.md
Instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.
AgentTeams AGENTS.md
Instructions for agentscope-ai/AgentTeams, covering agentteams codebase navigation guide, what is agentteams, project structure, runtime model and manager/agent/ layout (built into manager images).
memstack CLAUDE.md
Instructions for cwinvestments/memstack, covering memstack™ skill loader, always call findskill before, always call listskills when, do not call findskill for and priority.
tree-sitter-analyzer CLAUDE.md
Instructions for aimasteracc/tree-sitter-analyzer, covering ruflo — claude code configuration, rules, test quality rules — locked (2026-06-28), t-1: no new test files for existing plugins (blocker) and t-2: no weak assertions — ratchet-enforced (blocker).
LynxPrompt CLAUDE.md
Instructions for GeiserX/LynxPrompt, covering claude.md - ai agent instructions for lynxprompt, 🚀 release process (critical - read carefully), understanding the release pipeline, step-by-step release process and 1. switch to develop branch.