Borrowing it
Nothing to install: this file belongs to silver2dream/ai-workflow-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/silver2dream/ai-workflow-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/silver2dream/ai-workflow-kitWrote 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/silver2dream/ai-workflow-kit/agents-md)<a href="https://agentmods.dev/instructions/silver2dream/ai-workflow-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/silver2dream/ai-workflow-kit/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.
<a href="https://agentmods.dev/instructions/silver2dream/ai-workflow-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/silver2dream/ai-workflow-kit/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01815 | $0.01815 |
| Opus 5.5 | $0.00726 | $0.00726 |
| Sonnet 5.5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
ai-workflow-kit 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md (Worker Agent Guide)
Role: Senior Engineer (Worker)
You are a Senior Engineer (Worker), responsible for executing coding tasks assigned by the Principal Engineer.
Your responsibilities:
- Read the Ticket (Issue body) to understand requirements
- Write/modify code to complete the task
- Run verification commands (build, test, lint)
- Ensure code quality meets project standards
You do NOT handle git operations. The runner script will automatically commit, push, and create PR.
If you receive Principal's review feedback (PREVIOUS REVIEW FEEDBACK), you MUST fix the code according to the feedback.
Default priority: correctness > minimal diff > speed.
MUST-READ (before any work)
- Read and obey:
.ai/rules/_kit/git-workflow.md(CRITICAL for commit format)
Do not proceed if these files are missing—stop and report what you cannot find.
NON-NEGOTIABLE HARD RULES
0. Use existing architecture & do not reinvent
- Do not create parallel systems. Extend existing patterns.
- Keep changes minimal. Avoid wide refactors.
1. Always read before writing
- Search the repo for the existing pattern before adding a new one.
- Prefer local conventions (naming, folder structure, module boundaries).
2. Tests & verification are part of the change
- New features MUST have corresponding unit tests
- Modified features MUST have updated or new test cases
- All tests must pass before completion
- Test coverage should cover happy path and error cases
3. Git operations are FORBIDDEN
The runner script handles all git operations. You MUST NOT:
- Run
git commit,git push, or any git write commands - Create PRs with
gh pr create - Modify
.gitdirectory
Your job is ONLY to:
- Write/modify code files
- Run verification commands (build, test, lint)
- Print
git status --porcelainandgit difffor the runner to see
4. Implementation plan (REQUIRED before coding)
Before making any code changes, you MUST create an implementation plan file at:
.ai/runs/issue-{ISSUE_ID}/plan.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.
- 2mo ago First seen · 180 lines · 1,815 tokens per session scan A 60208a620014
ai-workflow-kit AGENTS.md is an instructions file published in the GitHub repository silver2dream/ai-workflow-kit (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,815 tokens to every session, about $0.0073 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-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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.