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/vladm3105/aidoc-flow-framework/agents-mdgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/agents-md)<a href="https://agentmods.dev/instructions/vladm3105/aidoc-flow-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/vladm3105/aidoc-flow-framework/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.01323 | $0.01323 |
| Opus 5 | $0.00661 | $0.00661 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
aidoc-flow-framework 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working agreement for AI coding agents on aidoc-flow-framework
Orients any AI agent (Claude Code, Codex, Gemini CLI, Copilot, Hermes, custom)
working on this repo. CLAUDE.md is the full working agreement;
this file is the short orientation plus the rules that are most often missed.
Where the two disagree, CLAUDE.md wins — fix this file.
What this repo is
One engine-agnostic specification (framework/) and two independent platforms
that consume it: Hermes (MCP server, platforms/hermes/) and the Claude
Code plugin (platforms/claude-code-plugin/). The spec defines the 8-layer SDD
flow (BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code). Both platforms
pass the same shared conformance suite (tests/conformance/).
Filing gaps — open a GitHub issue
When you find a defect, inconsistency, or missing capability, open a GitHub issue on this repo. That is the whole rule — there is one surface.
Capture at discovery still applies, unchanged: open the issue when you find it, not in a "later PR". What moved is the surface, not the timing.
The issue body carries: reproduction at file:line, blast radius run rather
than assumed, why it was hard to diagnose, a suggested fix, and what is not
broken. One issue per defect. Move the analysis verbatim — never summarise a
finding into an issue, because a re-derived finding silently contracts.
Search before filing (gh issue list --search … --state all); comment on an
open match instead of duplicating it; a closed match gets a new issue
cross-linked as a regression, never a reopen. The merge closes the issue — the PR
body carries Closes #N, one keyword per reference (Closes #A and #B closes
only #A).
Use gh issue create --body-file -, never --body -: the latter publishes a
literal -, exits 0, and prints a URL, so it looks like it worked. Read the
artifact back — gh issue view <N> --json body --jq '.body | length' — a
non-zero length is the only proof it published.
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 · 101 lines · 1,323 tokens per session scan A 19517c832a04
aidoc-flow-framework AGENTS.md is an instructions file published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 1,323 tokens to every session, about $0.0066 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.