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/p1va/symbols/agents-mdgit clone --depth 1 https://github.com/p1va/symbolsWrote 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/p1va/symbols/agents-md)<a href="https://agentmods.dev/instructions/p1va/symbols/agents-md"><img src="https://agentmods.dev/badge/instructions/p1va/symbols/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.01752 | $0.01752 |
| Opus 5 | $0.00876 | $0.00876 |
| Sonnet 5 | $0.00350 | $0.00350 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
symbols 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 4d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
This file captures the durable principles for working on Symbols. Keep it short, current, and operational; historical plans are useful evidence, not active policy.
Current sources of truth:
- README.md for the public tool, resource, skill, and install surface
- docs/MAINTENANCE.md for accepted follow-up work
- docs/PLUGIN_CONTROL_PLANE_DIRECTION.md for the product and distribution boundary
- docs/LANGUAGE_SERVER_REFERENCE_PLAN.md for per-language guidance
- docs/CODE_QUALITY_ROADMAP.md for the rationale behind the current TypeScript contracts
When an old plan conflicts with this file, current code, or the maintenance backlog, update or archive the old plan instead of preserving two policies.
Product Boundary
Symbols is a lightweight MCP bridge to Language Servers.
Keep the responsibilities split like this:
- skills and plugin assets carry installation and troubleshooting guidance
language-servers.yamlis desired state- MCP resources expose effective config and runtime state
- MCP tools perform navigation, inspection, search, rename, diagnostics, and control-plane actions
Do not grow Symbols into:
- a managed installer framework
- a large MCP recipe catalog
- a broad workflow product with shell, file, or memory tooling
Architecture And Contracts
The intended flow is:
tools -> preparation -> operations -> session -> client
- tools parse MCP input, keep file-to-session routing visible, and render output
- preparation validates workspace, file, and position semantics and resolves session-bound targets
- operations issue protocol requests and normalize protocol responses
- sessions own process and document lifecycle
- the client owns transport and LSP initialization plumbing
Keep these contracts explicit:
- use official typed LSP request descriptors so method, parameters, and result types cannot drift independently
- treat Language Server responses as external data; normalize each supported protocol union once at the operations boundary and expose one honest internal shape
- MCP inputs are one-based and LSP coordinates are zero-based; convert once during preparation and once at the user-facing render edge
- enrichment returns exactly one result per request in input order
- operations and lifecycle callbacks return values or throw; preserve the
original error as
cause, and useResultonly when callers genuinely branch - cleanup belongs in
finallypaths and must not replace the primary failure
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.
- 4d ago First seen · 216 lines · 1,752 tokens per session scan A d46987c5af25
symbols AGENTS.md is an instructions file published in the GitHub repository p1va/symbols (3 stars, last pushed 1mo ago), licensed MIT. It adds 1,752 tokens to every session, about $0.0088 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
optionsahoy-mcp AGENTS.md
AGENTS.md instructions for AlvisoOculus/optionsahoy-mcp, covering agents.md, what this repo is, what an agent should do with this server, how an agent connects and required-input discipline.
optionsahoy-mcp GEMINI.md
Gemini CLI instructions for AlvisoOculus/optionsahoy-mcp, covering optionsahoy equity-compensation tools, tools and usage rules.
skills AGENTS.md
AGENTS.md instructions for getanyapi-com/skills: This repository publishes customer-facing agent skills for the AnyAPI ecosystem. The authoritative wiring, contract invariants, impact classifier, repository gates, and rollout order live in the main repository's ECOSYSTEM.md.
horizon-shield GEMINI.md
Gemini CLI instructions for ogasurfproject-jpg/horizon-shield: You have the HORIZON SHIELD tools available. HORIZON SHIELD audits Japanese construction and renovation cost estimates against the open JCCDB dataset (95,403 line items) and returns fair-price references as tamper-evident, independently recomputable…
charming-mcp AGENTS.md
AGENTS.md instructions for tambo-labs/charming-mcp, covering agents.md, connect first, two authoring paths, build flow and the app contract.
python-code-validator AGENTS.md
AGENTS.md instructions for jkanselaar/python-code-validator, covering python you write here gets checked, say what the code is for, before you write it, while you write, when something comes back wrong and before you present anything.