Borrowing it
Nothing to install: this file belongs to Strategic-Automation/violin. 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/Strategic-Automation/violin/master/AGENTS.mdgit clone --depth 1 https://github.com/Strategic-Automation/violinWrote 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/strategic-automation/violin/agents-md)<a href="https://agentmods.dev/instructions/strategic-automation/violin/agents-md"><img src="https://agentmods.dev/badge/instructions/strategic-automation/violin/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/strategic-automation/violin/agents-md"><img src="https://agentmods.dev/badge/instructions/strategic-automation/violin/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.02590 | $0.02590 |
| Opus 5.5 | $0.01036 | $0.01036 |
| Sonnet 5.5 | $0.00518 | $0.00518 |
| Haiku 4.5 | $0.00259 | $0.00259 |
Grade A, and why
violin 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 11d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Violin repository guidance
Violin is a supervised Hermes pentest profile. This file guides development and maintenance of the directory tree containing it. Follow more specific AGENTS.md files for their subtrees; direct system, developer, and user instructions take precedence. Repository development is distinct from running an engagement.
Start here
- Confirm the working directory, branch, base commit, and existing changes before editing. Preserve unrelated work. Keep review-only requests read-only.
- Run commands below from the project directory containing this file and
pyproject.toml. In copied benchmark trees, Git may resolve to a parent checkout; do not mistake that parent's commit or clean status for the snapshot's identity. - Use the Python version in
.python-version, consistent withrequires-pythoninpyproject.tomland the CI matrix. Resolve discrepancies before changing runtime versions; do not upgrade Python as an incidental documentation fix. - Install development dependencies with
uv sync --dev; useuv runand the project.venv. Keep dependency and lockfile updates intentional. - Read CONTRIBUTING.md for contribution conventions, docs/BENCHMARKS.md for evaluation methodology, and .github/workflows/ci.yml for automated checks. Keep this guidance aligned with those files when workflows change.
Where changes belong
plugins/violin_guard/: Hermes tools, schemas, execution gates, and state.scripts/: administrative CLI, smoke checks, and maintenance helpers.skills/: routed skills and domain playbooks; shared templates and references remain underskills/pentest/. Follow the routing map inCONTRIBUTING.md.benchmark/: runner, host-side evaluator, calibration, and aggregation.tests/: guard, benchmark, CLI, and documentation contract tests.
Prefer the smallest cohesive change. Reuse existing project helpers, the standard library, and declared dependencies before adding custom parsing or abstractions. Do not add wrappers or split modules without a concrete maintenance benefit.
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.
- 11d ago Changed · +125 lines · +979 tokens per session 92090b53a24d
- 1mo ago Changed · +31 lines · +359 tokens per session 3b1c645f1664
- 1mo ago Changed · +4 lines · +140 tokens per session 9485834a851a
- 1mo ago First seen · 44 lines · 1,112 tokens per session scan A 80000b13b5d1
violin AGENTS.md is an instructions file published in the GitHub repository Strategic-Automation/violin (152 stars, last pushed 2d ago), licensed MIT. It adds 2,590 tokens to every session, about $0.0104 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).