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/mootikins/figurehead-rs/agents-mdgit clone --depth 1 https://github.com/Mootikins/figurehead-rsWrote 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/mootikins/figurehead-rs/agents-md)<a href="https://agentmods.dev/instructions/mootikins/figurehead-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/mootikins/figurehead-rs/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.01763 | $0.01763 |
| Opus 5 | $0.00881 | $0.00881 |
| Sonnet 5 | $0.00353 | $0.00353 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade A, and why
figurehead-rs 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 5d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Development Guidelines
This document provides guidelines for AI agents working on the Figurehead project.
Architecture Overview
Figurehead follows a modular, plugin-based architecture inspired by mermaid.js:
Input → Detector → Parser → Database → Layout → Renderer → Output
Core Components
-
Core Traits (
src/core/): Define interfaces for all componentsDiagram: Main entry point for each diagram typeDetector: Identifies diagram types from markupParser: Parses markup using chumskyDatabase: Stores nodes, edges, and diagram dataLayoutAlgorithm: Arranges elements in coordinate spaceRenderer: Generates output (ASCII, SVG, etc.)
-
Plugins (
src/plugins/): Implementations for specific diagram types- Each plugin implements all core traits
- Currently: flowchart (basic implementation)
- Future: sequence, class, gantt charts
-
Pipeline: Data flows through stages using the traits
Development Principles
SOLID Principles
- Single Responsibility: Each trait/component has one purpose
- Open/Closed: Extensible through plugins, closed for modification
- Liskov Substitution: All implementations can replace their interfaces
- Interface Segregation: Small, focused traits
- Dependency Inversion: Depend on abstractions, not concretions
Rust Idioms
- Use
match, iterators, and&[Type]instead ofVecwhere possible - Prefer
Result<T, E>over exceptions - Use trait objects (
dyn Trait) for runtime polymorphism - Leverage zero-cost abstractions and compile-time guarantees
Test-Driven Development (TDD)
- Write failing tests first
- Implement minimal code to make tests pass
- Refactor while maintaining test coverage
- Use property-based testing for complex logic
Implementation Guidelines
When Adding New Diagram Types
- Create Plugin Structure:
// src/plugins/newtype/mod.rs pub struct NewTypeDiagram; impl Diagram for NewTypeDiagram { type Database = NewTypeDatabase; type Parser = NewTypeParser; type Renderer = NewTypeRenderer; // ... implement all methods }
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.
- 5d ago First seen · 261 lines · 1,763 tokens per session scan A 1b79f5e5227a
figurehead-rs AGENTS.md is an instructions file published in the GitHub repository Mootikins/figurehead-rs (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,763 tokens to every session, about $0.0088 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
vscode buildNext.instructions.md
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).
spec-kit AGENTS.md
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
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.
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).