Borrowing it
Nothing to install: this file belongs to pandoscope/skills. 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/pandoscope/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/pandoscope/skillsWrote 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/pandoscope/skills/agents-md)<a href="https://agentmods.dev/instructions/pandoscope/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/pandoscope/skills/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.04318 | $0.04318 |
| Opus 5 | $0.02159 | $0.02159 |
| Sonnet 5 | $0.00864 | $0.00864 |
| Haiku 4.5 | $0.00432 | $0.00432 |
Grade A, and why
skills 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.
How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills — Agent Guidelines
Repo: https://github.com/frankify-app/skills
Project Specifics
Terminology
Ubiquitous language is defined in docs/glossary/. Use
uvx disambiguate==0.3.0 <term>
to get a topologically ordered glossary disambiguating all relevant terms to understand the given term.
Before working on a ticket, run:
uvx disambiguate==0.3.0 --from <ticket-file>
or for GitHub issues:
ghx issue view <number> --json body -q .body | uvx disambiguate==0.3.0 --from -
to resolve all referenced terms at once.
Architecture
Read docs/architecture.md before touching any code.
Rules
- Small, single-purpose files
- Prose (skills, ADRs, tickets, docs): as short as possible, prefer caveman mode — unless precision or understandability suffers
- Readability over brevity — straightforward, easy-to-follow code. No compact "one-liners" stretching across multiple lines (e.g. nested ternaries). Stretching across multiple lines is only allowed if it aids readability.
- When removing a feature, erase every mention of it — docs, help text, comments, tests. Don't leave "no longer supported" notes: readers who never knew it existed pay to learn it did. State what is, not what stopped being. (Migration notes belong in the commit's
BREAKING CHANGE:footer, which is where someone upgrading looks.) - In prose, don't state facts maintained elsewhere — counts ("the seven examples above"), far positional references, restated section names. Link the target instead. Immediate-adjacency words ("the examples above", "the following table") are fine — they only break if adjacency breaks.
- All routes and non-trivial functions: docstring contracts (params, returns, errors)
- Test cases cover edge cases and every
@returnsline
Errors
- Forward all errors with full detail + variable values, never swallow or catch, let exceptions propagate with their full traceback to make proper debugging possible
- Never catch exceptions if they are actual errors that can't be handled
- Include relevant variable values in error messages, e.g. for JS/TS:
"Failed to fetch peers for workspace_id=${workspace_id}: ${e}"
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 · 314 lines · 4,318 tokens per session scan A fd0c99ecbe6f
skills AGENTS.md is an instructions file published in the GitHub repository pandoscope/skills (1 stars, last pushed 2d ago), licensed MIT. It adds 4,318 tokens to every session, about $0.0216 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.