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/bikeread/promethos/agents-mdgit clone --depth 1 https://github.com/bikeread/promethosWrote 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/bikeread/promethos/agents-md)<a href="https://agentmods.dev/instructions/bikeread/promethos/agents-md"><img src="https://agentmods.dev/badge/instructions/bikeread/promethos/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.00697 | $0.00697 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
promethos 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
skills/ is the canonical library. Each skill lives in
skills/<skill-name>/SKILL.md; supporting files should stay beside it,
typically in references/. Name skills with short, task-first, verb-led ids
using lowercase letters, digits, and hyphens only. Keep bootstrap and
harness-mapping material under the routing/bootstrap skill directory rather
than scattering it across the library. Contributor and platform docs live in
docs/, CONTRIBUTING.md, .codex/INSTALL.md, GEMINI.md, and
gemini-extension.json. Automation lives in scripts/ and
.github/workflows/.
Build, Test, and Development Commands
There is no compiled build or local server in this repository. The required validation commands are:
./scripts/validate-skills.sh
python3 ./scripts/check-repo-docs.py
This checks for exactly one SKILL.md per top-level skill directory, required
frontmatter, required headings, duplicate skill names, and bootstrap reference
files, plus required public-facing docs and local Markdown links. If you change
install or platform docs, also run a harness-specific smoke check, for example
ls -la ~/.agents/skills/promethos for Codex.
Coding Style & Naming Conventions
Keep content portable across harnesses. Do not fork the same skill body per
provider; put tool-mapping notes in the routing/bootstrap skill's
references/ directory. Every SKILL.md must define name and
description. Keep name + description at 250 characters or less, and put
trigger language in description instead of a separate when_to_use field.
Then include the exact headings enforced by the validator: # Goal,
## Inputs, ## Non-Goals, ## Workflow, ## Output Contract,
## Escalation, and ## Common Failure Modes. Keep SKILL.md concise and
move long examples or variant-specific detail into references/. Follow the
existing Markdown style: short paragraphs, direct bullets, and wrapped lines.
Shell scripts should remain Bash with set -euo pipefail.
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 · 61 lines · 697 tokens per session scan A 5bd9c05f4f61
promethos AGENTS.md is an instructions file published in the GitHub repository bikeread/promethos (33 stars, last pushed 5mo ago), licensed MIT. It adds 697 tokens to every session, about $0.0035 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-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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.