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/quangdang46/looper_rust/agents-mdgit clone --depth 1 https://github.com/quangdang46/looper_rustWrote 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/quangdang46/looper_rust/agents-md)<a href="https://agentmods.dev/instructions/quangdang46/looper_rust/agents-md"><img src="https://agentmods.dev/badge/instructions/quangdang46/looper_rust/agents-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.00539 | $0.00539 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
looper_rust 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 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Looper Rust — AI Agent Guidelines
Build
cargo build --release # Release build (all targets)
cargo build # Debug build
cargo check --workspace # Fast type-check (recommended during dev)
Test
cargo test --workspace # All tests
cargo test -p <crate> # Single crate
cargo test -p <crate> -- <name> # Single test by name
Lint
cargo fmt --check # Format check
cargo fmt # Auto-format
cargo clippy --workspace -- -D warnings # Full lint
cargo clippy -p <crate> # Single crate
Workspace Members
| Crate | Type | Description |
|---|---|---|
| looper-types | lib | Domain enums, state machines, core types |
| looper-config | lib | Config loading, validation, merge, disclosure |
| looper-storage | lib | SQLite repositories, migrations, event log |
| looper-service | lib | Loop, Run, Project business logic |
| looper-github | lib | GitHub gateway via gh CLI |
| looper-git | lib | Git worktree management |
| looper-agent | lib | Agent executor (5 vendors) |
| looper-scheduler | lib | Tick loop, queue claim, discovery |
| looper-runner | lib | Planner, Reviewer, Fixer, Worker, Coordinator |
| looper-api | lib | axum REST server, auth, envelope |
| looper-webhook | lib | Webhook forwarder, event routing |
| looper-infra | lib | Bootstrap, runtime, notifications |
| looperd | bin | Daemon binary |
| looper-cli | bin | CLI binary |
| looper-net | bin | Loopernet cloud server binary |
| diffanchor | lib | Diff parsing and anchor validation |
Directory Layout
looper_rust/
├── Cargo.toml # Workspace root
├── crates/ # All crates
│ ├── looper-types/ # Phase 1
│ ├── looper-config/ # Phase 2
│ ├── ...
├── legacy/ # Go reference (gitignored)
├── PORTING-TO-RUST/
│ ├── LOOPER_RUST_DESIGN.md # Architecture design
│ └── specs/ # Behavioral specs
├── .github/workflows/ # CI/CD
└── .beads/ # Task tracking
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 · 65 lines · 539 tokens per session scan A e87dcb3a17c4
looper_rust AGENTS.md is an instructions file published in the GitHub repository quangdang46/looper_rust (4 stars, last pushed 15d ago), licensed MIT. It adds 539 tokens to every session, about $0.0027 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 instructions, from other repositories
codemark GEMINI.md
Instructions for DanielCardonaRojas/codemark, covering development workflow and debugging with the tui logging system.
NEEDLE CLAUDE.md
Instructions for jedarden/NEEDLE, covering needle project conventions, msrv, module dependency graph, code style and testing.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
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.
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.