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/roblovestech/agenticflywheel/agents-mdgit clone --depth 1 https://github.com/RobLovesTech/AgenticFlyWheelWrote 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/roblovestech/agenticflywheel/agents-md)<a href="https://agentmods.dev/instructions/roblovestech/agenticflywheel/agents-md"><img src="https://agentmods.dev/badge/instructions/roblovestech/agenticflywheel/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.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
AgenticFlyWheel 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Root docs such as
README.md,spec/AIP_FRAMEWORK.md, andspec/EXECUTION_LAYER.mddefine the AgenticFlywheel control plane and runtime layer. prompts/contains the prompt workflows (e.g.SYSTEM_BOOTSTRAP.md,AIP_NEW.md,IMPLEMENTATION_AUDIT.md,OFFICE_HOURS.md,SHIP.md) that agents run inside AI tools.templates/holds reusable AIP and AIP‑Lite packet templates (templates/aip/**,templates/aip-lite/**) plus config templates undertemplates/config/**.features/REGISTRY.schema.jsondefines the schema for downstream feature registries; keep it backward compatible.
Build, Test, and Development Flow
- This repository is docs‑ and schema‑only; there is no compile or build step.
- To exercise flows, run the prompts in
prompts/against a sample repo (start withSYSTEM_BOOTSTRAP.md, thenOFFICE_HOURS.md/AUTOPLAN.md, thenTUTORIAL_FIRST_AIP.md, thenIMPLEMENTATION_AUDIT.mdbefore packet closure). - When editing schemas, validate them with your preferred JSON Schema tool (e.g.
ajv,spectral) before opening a PR.
Coding Style & Naming Conventions
- Use Markdown with ATX headings (
#,##) and concise, instructional language. - Use 2‑space indentation for YAML; format JSON schemas with 2‑space indentation and sorted keys where practical.
- Prompt files in
prompts/use UPPER_SNAKE_CASE names (e.g.AIP_COLLAB.md); new prompts must follow this pattern. - Template and spec paths in docs should be explicit (e.g.
docs/Agent Implementation Packets/<feature-slug>/CHECKLIST.yaml).
Testing Guidelines
- For prompt changes, manually walk through at least one end‑to‑end flow (bootstrap → AIP creation → checklist validation) and note results in the PR.
- For schema updates (
features/REGISTRY.schema.json,templates/aip/CHECKLIST.schema.json), add or update example payloads and validate them. - Avoid breaking existing downstream contracts; prefer additive changes and document any deprecations in
spec/AIP_FRAMEWORK.md.
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 · 33 lines · 660 tokens per session scan A 999f149129d9
AgenticFlyWheel AGENTS.md is an instructions file published in the GitHub repository RobLovesTech/AgenticFlyWheel (2 stars, last pushed 4mo ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 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
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.
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.
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).
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.