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/stbenjam/skillsaw/copilot-instructionsgit clone --depth 1 https://github.com/stbenjam/skillsawWrote 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/stbenjam/skillsaw/copilot-instructions)<a href="https://agentmods.dev/instructions/stbenjam/skillsaw/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/stbenjam/skillsaw/copilot-instructions.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.04542 | $0.04542 |
| Opus 5 | $0.02271 | $0.02271 |
| Sonnet 5 | $0.00908 | $0.00908 |
| Haiku 4.5 | $0.00454 | $0.00454 |
Grade A, and why
skillsaw copilot-instructions.md scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`subprocess.CompletedProcess` stand-in. Spawning an interpreter per call cost Copies of this mod
1 near-identical copy found in the catalogue:
- skillsaw AGENTS.md — 98% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow these rules when developing skillsaw, a configurable, rule-based linter for agentic contextual building blocks.
Pre-push Checklist
CRITICAL: You MUST always run these steps before pushing changes.
- Ensure branch is up to date with UPSTREAM (stbenjam/skillsaw) — check git remotes then merge upstream's main.
- Run
make test— run the full test suite and ensure all tests pass. Never assume a problem is pre-existing; follow the boyscout rule and fix it anyway. - Run
make lint— check formatting (or runmake formatto fix it). - Run
make update— regenerate all generated files (must come after version bump). - Test against
openshift-eng/ai-helpers: clone it, runskillsaw, and ensure exit 0.
Pre-PR Checklist
Follow these checks before opening a PR:
- Check whether documentation is up to date for the changes on this branch.
- Example: you add a new feature, flag, or lint type.
Action: update
README.mdto include this. - Example: you encounter a problem during development you must keep for later.
Action: update
.apm/instructionsand runmake update.
- Example: you add a new feature, flag, or lint type.
Action: update
- Verify test coverage on a new feature, flag, lint type or bug fix is complete.
- Bug fixes must include regression protection.
- New features, linters, and rules need integration test coverage WITH fixtures (see testing rules).
Authoring Agentic Context
When you create or edit a skill, slash command, agent, hook, or instruction
file in this repo, load the skillsaw-lint skill and follow it: lint the
file with .venv/bin/skillsaw lint <path>, apply fixes, and re-lint until
clean before you finish. We ship the linter — our own context must pass it.
Post-PR Checklist
After opening a PR, keep monitoring for feedback from CodeRabbit, Gemini, and stbenjam. You may stop monitoring 20 minutes after you push a PR. Review and handle valid feedback that comes in.
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 · 334 lines · 4,542 tokens per session scan A feef3aff899d
skillsaw copilot-instructions.md is an instructions file published in the GitHub repository stbenjam/skillsaw (59 stars, last pushed 4d ago), licensed Apache-2.0. It adds 4,542 tokens to every session, about $0.0227 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.