Borrowing it
Nothing to install: this file belongs to adiasg/guitar-tabs. 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/adiasg/guitar-tabs/main/AGENTS.mdgit clone --depth 1 https://github.com/adiasg/guitar-tabsWrote 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/adiasg/guitar-tabs/agents-md)<a href="https://agentmods.dev/instructions/adiasg/guitar-tabs/agents-md"><img src="https://agentmods.dev/badge/instructions/adiasg/guitar-tabs/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.1 | $0.00465 | $0.00465 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
guitar-tabs 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 8d 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.
What it actually says
Guitar Tab System
This repository contains guitar tab sheets and a system for generating those tab sheets.
Tab sheets
Sheet format
Tab sheets are Markdown formatted, with the actual tabs or chords in code blocks.
File structure
Tab sheets should contain the following in this order:
- The song name & artist name
- A table containing:
- key & scale of the song
- time signature
- Ordering of song sections (e.g. verse, chorus, bridge, solo)
- A Markdown section for each song section
- chords + tabs for rhythm sections, tabs for lead plucking/solo sections
Example tab sheet header:
## Treasure — Bruno Mars
<table>
<tbody>
<tr><td><strong>Key & scale</strong></td><td>Ab major (Ab Ionian: Ab Bb C Db Eb F G)</td></tr>
<tr><td><strong>Time signature</strong></td><td>4/4</td></tr>
<tr><td><strong>Tuning</strong></td><td>Standard (E A D G B E)</td></tr>
<tr><td><strong>Tempo</strong></td><td>~116 BPM</td></tr>
</tbody>
</table>
### Song structure
Intro → Verse 1 → Pre-chorus → Chorus → Verse 2 → Pre-chorus → Chorus → Bridge → Final Chorus/Outro
Notes:
- Tabs should always show all six guitar strings.
- When both tabs & chords are provided, place the chords above the tabs.
File organization
- Place the tab sheets at
/tabs/{artist_name}/{song_name}. - When a new request comes in, always check that the sheet doesn't already exist so we don't duplicate work.
Generating tabs
An MCP is available in guitar-tabs-mcp for scraping tabs, and it's Cursor config is at .cursor/mcp.json. It requires a venv install, which is given in the Makefile. All other processing is done inside Cursor with it's AI agent chat.
Setup
Set up instructions are provided in the README
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.
- 8d ago First seen · 55 lines · 465 tokens per session scan A 719e2296a9fc
guitar-tabs AGENTS.md is an instructions file published in the GitHub repository adiasg/guitar-tabs (5 stars, last pushed 11mo ago), licensed MIT. It adds 465 tokens to every session, about $0.0023 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
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.
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.
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).
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).
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.
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.