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/blizzy78/mcp-task-manager/run-testsgit clone --depth 1 https://github.com/blizzy78/mcp-task-managerWhat 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.00035 | $0.00035 |
| Opus 5 | $0.00017 | $0.00017 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
mcp-task-manager run-tests.instructions.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 2d 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
The command to run tests only is pnpm test.
The command to run tests with code coverage is pnpm test:coverage.
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.
- 2d ago First seen · 6 lines · 35 tokens per session scan A 8444a84d0b89
mcp-task-manager run-tests.instructions.md is an instructions file published in the GitHub repository blizzy78/mcp-task-manager (4 stars, last pushed 12mo ago), licensed MIT. It adds 35 tokens to every session, about $0.0002 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
mcp-elicit CLAUDE.md
Claude Code instructions for blizzy78/mcp-elicit, covering elicitation mcp server, project description, high-level architecture, transport layer architecture and tool architecture.
mini-swe-agent copilot-instructions.md
Copilot instructions for SWE-agent/mini-swe-agent, covering style guide, test style, bad and good.
Octop AGENTS.md
Instructions for TencentCloud/Octop, covering agents.md, 1. collaboration principles, think before writing, simplicity first and surgical edits.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
relay AGENTS.md
Instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
braindb CLAUDE.md
Instructions for dimknaf/braindb, covering braindb — claude instructions, ⚠ tool priority — read this first, it overrides habit, at the start of every session, 1. get always-on rules (behavioral guidelines) and project structure.