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/bgpkit/monocle/agents-mdgit clone --depth 1 https://github.com/bgpkit/monocleWhat 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.01529 | $0.01529 |
| Opus 5 | $0.00764 | $0.00764 |
| Sonnet 5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
monocle 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monocle - Agent Instructions
This document provides guidelines for AI coding agents working on the monocle codebase.
Build, Lint, and Test Commands
Quick Reference
# Format code (always run after editing)
cargo fmt
# Build with default features (cli)
cargo build
# Run all tests
cargo test --all-features
# Run clippy with all warnings as errors
cargo clippy --all-features -- -D warnings
# Run a single test by name
cargo test test_name
cargo test lens::time::tests::test_parse_unix
# Run tests for a specific module
cargo test lens::rpki
# Run tests with output visible
cargo test test_name -- --nocapture
CI Checks (run before committing)
The GitHub Actions workflow runs these checks on PRs:
cargo fmt --check # Check formatting
cargo clippy --all-targets --all-features -- -D warnings # Lint
cargo test --all-features --verbose # All tests
Code Style Guidelines
Lints
The crate enforces strict lints in lib.rs:
#![deny(clippy::unwrap_used)]
#![deny(clippy::expect_used)]
Use ? operator or explicit error handling instead of .unwrap() or .expect().
Import Organization
Group imports in this order, separated by blank lines:
- Standard library (
std::) - External crates
- Internal crate modules (
crate::,super::)
Naming Conventions
| Item | Convention | Example |
|---|---|---|
| Lens struct | {Name}Lens |
TimeLens, RpkiLens, InspectLens |
| Args struct | {Name}{Op}Args |
TimeParseArgs, RpkiValidationArgs |
| Result struct | {Name}{Op}Result |
As2relSearchResult, InspectResult |
| Module name | snake_case | as2rel, pfx2as, inspect |
| Constants | SCREAMING_SNAKE_CASE | DEFAULT_RPKI_CACHE_TTL |
Error Handling
Use anyhow::Result for lens methods with descriptive error messages:
// Good
Err(anyhow!("Invalid prefix format: {}. Expected CIDR notation (e.g., 1.1.1.0/24)", input))
// Bad
Err(anyhow!("invalid input"))
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.
- 2d ago First seen · 217 lines · 1,529 tokens per session scan A afcb55a83976
monocle AGENTS.md is an instructions file published in the GitHub repository bgpkit/monocle (183 stars, last pushed 15d ago), licensed MIT. It adds 1,529 tokens to every session, about $0.0076 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.