formanator: Instructions file for Codex

AGENTS.md

formanator AGENTS.md is an instructions file for Codex, OpenCode from timrogers/formanator. It costs 471 tokens per session, scanned A, original, MIT.

Repository instructions for formanator, a Rust command-line tool for working with Forma claims, with optional MCP server support. They describe the code layout, development rules, and checks.

In plain words
What is it for?
They help developers find the right Rust files, run formatting and tests, and keep local changes aligned with the project workflow.
Why use it?
They give coding agents a shared reference for making focused changes and validating them the same way as GitHub Actions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is timrogers/formanator's own configuration. It tells Codex and OpenCode how to work on formanator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything formanator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to timrogers/formanator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/timrogers/formanator/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/timrogers/formanator

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for formanator AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/timrogers/formanator/agents-md/github.svg)](https://agentmods.dev/instructions/timrogers/formanator/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/timrogers/formanator/agents-md"><img src="https://agentmods.dev/badge/instructions/timrogers/formanator/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for formanator AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/timrogers/formanator/agents-md"><img src="https://agentmods.dev/badge/instructions/timrogers/formanator/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 471 This file is loaded in full into every session.
When invoked 471 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00471 $0.00471
Opus 5.5 $0.00188 $0.00188
Sonnet 5.5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

Measured 2mo ago against content hash 8d885df1b46c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

formanator 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 2mo 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.

AGENTS.md · 48 lines

What it actually says

AGENTS.md

Repository overview

  • formanator is a Rust CLI for working with Forma claims, with optional MCP server support.
  • src/main.rs is the binary entry point and dispatches subcommands.
  • src/cli.rs defines the Clap CLI surface.
  • src/commands/ contains one handler per subcommand.
  • src/lib.rs exposes shared modules such as Forma API access, claim handling, config, prompts, LLM integration, and MCP support.
  • The default feature set includes mcp; the crate targets Rust edition 2024 and has an MSRV of Rust 1.94.

Working in this repository

  • Keep changes small and focused on the requested task.
  • Follow existing Rust patterns and keep command wiring in src/cli.rs, src/main.rs, and src/commands/.
  • Update README.md when user-facing behavior or developer workflow changes.
  • Avoid changing dependencies or feature flags unless the task requires it.

Build, test, and validation

Use the same checks that GitHub Actions uses:

  1. Run pre-commit for formatting, linting, and repository hygiene:

    pre-commit run --all-files
    

    This covers the configured hook set, including cargo fmt --all, cargo check --locked --workspace --all-features --all-targets, cargo clippy --locked --workspace --all-features --all-targets -- -D warnings, codespell, and standard file checks.

  2. Run the test command used by the build workflow:

    cargo test --locked --all-features
    
  3. Run the release build used by the build workflow:

    cargo build --release --locked
    

GitHub Actions alignment

  • .github/workflows/pre-commit.yml runs the pre-commit checks on pushes and pull requests.
  • .github/workflows/build_and_release.yml runs cargo test --locked --all-features --target=<target> and cargo build --release --locked --target=<target> across Linux, macOS, and Windows targets on every push.
  • Tags matching v* additionally trigger GitHub release creation and Cargo publishing steps.
Changes

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.

  1. 2mo ago First seen · 48 lines · 471 tokens per session scan A 8d885df1b46c

Subscribe to this mod's changes

formanator AGENTS.md is an instructions file published in the GitHub repository timrogers/formanator (102 stars, last pushed 12d ago), licensed MIT. It adds 471 tokens to every session, about $0.0019 per session on Opus 5.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.

Related

formanator AGENTS.md compared with instructions from other repositories

formanator AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
formanator AGENTS.mdtimrogers/formanatorInstructions file10212d agoMITA471Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode