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/8090-inc/software-factory-plugin/agents-mdgit clone --depth 1 https://github.com/8090-inc/software-factory-pluginWrote 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/8090-inc/software-factory-plugin/agents-md)<a href="https://agentmods.dev/instructions/8090-inc/software-factory-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/8090-inc/software-factory-plugin/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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
software-factory-plugin 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guide for agents
Plugin registries (Cursor, Claude, Codex, Gemini, Kiro, Vercel)
Keywords/tags are plain strings; hyphens are a naming convention, not special array syntax. For official documentation links by platform (marketplaces, manifests, extensions, powers, skills), see docs/plugin-registry-documentation.md.
Pre-commit checks
This repo uses Husky so a pre-commit Git hook runs after a normal pnpm install.
- The hook runs
pnpm run test(Vitest), including integration tests for Work Order execution scripts undertests/work-order-execution-scripts.test.tsand validation tests undertests/validate.test.ts. - If tests fail, the commit is aborted; fix failures or update tests before committing.
Cloning fresh: run pnpm install once so the prepare script registers Husky hooks. If hooks were never installed, run pnpm exec husky (or pnpm install again).
Checks elsewhere
CI (.github/workflows/ci.yml) also runs pnpm run test among other steps, so pre-commit and CI stay aligned on the Vitest suite.
Pull requests
Open pull requests from a topic branch with a focused title, a concise summary of user-facing or registry-facing changes, and the exact validation commands run. Keep unrelated refactors, formatting churn, and generated-output changes out of the PR unless they are required for the change. Before requesting review, run the narrowest relevant checks plus pnpm run test for behavior changes or pnpm run validate/pnpm run verify:software-factory for plugin registry changes, and mention any check that could not be run.
Useful commands
| Command | Purpose |
|---|---|
pnpm run test |
Full Vitest suite (same as pre-commit) |
pnpm run lint |
ESLint (src/) + Markdown lint (plugins/) |
pnpm run verify:software-factory |
Software Factory plugin publishability |
pnpm run build |
Typecheck, hooks, validate, standalone exports |
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 · 32 lines · 493 tokens per session scan A d99243e82652
software-factory-plugin AGENTS.md is an instructions file published in the GitHub repository 8090-inc/software-factory-plugin (7 stars, last pushed 2mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 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.