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/mrwogu/promptscript/testinggit clone --depth 1 https://github.com/mrwogu/promptscriptWhat 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.00192 | $0.00192 |
| Opus 5 | $0.00096 | $0.00096 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
promptscript testing.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
Testing-specific rules
- Test files:
*.spec.tsnext to source - Follow AAA (Arrange, Act, Assert) pattern
- Framework: Vitest
- Target >90% coverage for libraries
- Use fixtures for parser tests
- When refactoring formatter section methods (e.g. splitting context() into project() + techStack() + architecture()), add a test verifying that ALL input block content still appears in the output — not just the newly extracted subsections
- Golden files are snapshots of correct behavior, not correct by definition — before regenerating golden files, verify the diff represents an intentional change, not a regression that golden files would lock 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.
- 2d ago First seen · 17 lines · 192 tokens per session scan A 21d6c3998c53
promptscript testing.instructions.md is an instructions file published in the GitHub repository mrwogu/promptscript (391 stars, last pushed 7d ago), licensed MIT. It adds 192 tokens to every session, about $0.0010 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
ai-prompts AGENTS.md
Instructions for liatrio-labs/ai-prompts, covering ai agent instructions, context marker, local skill scripts, standard workflow and initialize.
gortex CLAUDE.md
Instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
agent-toolkit AGENTS.md
Instructions for ulises-jeremias/agent-toolkit, covering agents.md — ai agent contract, what this toolkit does, repository structure, operating rules and how to add a skill.
core-ai CLAUDE.md
Instructions for helius-labs/core-ai, covering core ai, compiler-managed sync, mcp server pin, skill versioning and router surface maintenance.
ChatCrystal AGENTS.md
Instructions for ZengLiangYi/ChatCrystal, covering agents.md, project overview, commands, development (server port 3721 + client port 13721) and build for production.
core-ai AGENTS.md
Instructions for helius-labs/core-ai, covering core ai — agent instructions, repository overview, mcp server setup, api key setup and public tool surface.