Borrowing it
Nothing to install: this file belongs to krzysztofsurdy/code-virtuoso. 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/krzysztofsurdy/code-virtuoso/main/AGENTS.mdgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/agents-md)<a href="https://agentmods.dev/instructions/krzysztofsurdy/code-virtuoso/agents-md"><img src="https://agentmods.dev/badge/instructions/krzysztofsurdy/code-virtuoso/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/krzysztofsurdy/code-virtuoso/agents-md"><img src="https://agentmods.dev/badge/instructions/krzysztofsurdy/code-virtuoso/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.04964 | $0.04964 |
| Opus 5.5 | $0.01986 | $0.01986 |
| Sonnet 5.5 | $0.00993 | $0.00993 |
| Haiku 4.5 | $0.00496 | $0.00496 |
Grade A, and why
code-virtuoso 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 yesterday.
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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
@CONTRIBUTING.md
Agents are sub-agents - standalone markdown files that define a specialized role, its allowed tools, and its system prompt. Each agent file contains YAML frontmatter for configuration and a markdown body that is the agent's system prompt.
Where skills provide reference knowledge (patterns, checklists, component docs), agents are the actors that use that knowledge to perform work. A skill is a book on the shelf; an agent is the specialist who reads the book and applies it. Delegate to an agent when a task is well-scoped enough that a focused sub-agent will do it better than the orchestrating model switching context mid-conversation.
Contents
- Architecture
- Specialist agents
- Role agents
- Agent chaining patterns
- Running agents headless
- Conventions
- Plugins
Architecture
Agents follow a two-tier model:
Specialist agents handle a single, repeatable task type. They are typically read-only, stateless, and operate on whatever the caller hands them. Think of them as focused tools: investigate this, review that, scan for smells.
Role agents embody a team position. They carry a broader mandate and some keep persistent project-level memory across sessions. They own a domain ("the what", "the how", "the when") rather than a single task. A role is an agent plus the files in roles/<role>/ (templates, checklists, guides) that the agent reads by path when a task needs them. There is no role skill. See roles/README.md.
| Aspect | Specialist | Role |
|---|---|---|
| Scope | Single task type | Entire domain of responsibility |
| Knowledge | 0-2 preloaded skills | Reads roles/<role>/ files on demand, plus 0-2 preloaded skills |
| Memory | Stateless | Some use persistent memory for cross-session context |
| File modification | Read-only, except Implementer (source code) and Doc Writer (documentation) | Dev roles (Backend, Frontend) write code; the others are read-only |
| Isolation | Implementer uses a worktree; others run in place | Backend Dev and Frontend Dev use a worktree; others run in place |
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.
- yesterday Changed · +3 lines · +130 tokens per session df284b75e5bc
- 2d ago Changed · +68 lines · +1,795 tokens per session 0d41a023be2f
- 1mo ago First seen · 177 lines · 3,039 tokens per session scan A ab6ec0d6dc8e
code-virtuoso AGENTS.md is an instructions file published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. It adds 4,964 tokens to every session, about $0.0199 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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).