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/azure/azure-functions-skills/testinggit clone --depth 1 https://github.com/Azure/azure-functions-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/azure/azure-functions-skills/testing)<a href="https://agentmods.dev/instructions/azure/azure-functions-skills/testing"><img src="https://agentmods.dev/badge/instructions/azure/azure-functions-skills/testing.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.00262 | $0.00262 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
azure-functions-skills 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 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.
What it actually says
Testing Rules
Framework
- This project uses Vitest for all unit tests.
- Test files:
tests/*.test.ts - Fixtures:
tests/fixtures/ - Run:
npm test(single run) ornpm run test:watch(TDD mode)
TDD Workflow
- Red: Write a failing test that describes the expected behavior.
- Green: Write the minimal implementation to make the test pass.
- Refactor: Improve code quality without changing behavior.
- Repeat for each unit of work.
Test Quality
- Test behavior, not implementation details.
- Cover edge cases and boundary values.
- Include both happy path and error path tests.
- Use descriptive test names:
describe('functionName', () => { it('should do X when Y', ...) }). - Keep tests independent — no shared mutable state between tests.
Fixtures
- Bad-app fixtures for doctor checks live in
tests/fixtures/doctor-bad-apps/. - Expected results are documented in
tests/fixtures/doctor-bad-apps/expected-results.md. - When adding a new doctor check, add a corresponding fixture and update expected results.
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 · 34 lines · 262 tokens per session scan A 305b4f2b5a4e
azure-functions-skills testing.instructions.md is an instructions file published in the GitHub repository Azure/azure-functions-skills (16 stars, last pushed 7d ago), licensed MIT. It adds 262 tokens to every session, about $0.0013 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
wallfacer CLAUDE.md
Instructions for changkun/wallfacer: If you didn't add a test, you didn't fix a bug. Every bug fix must include a reproducible test that fails without the fix and passes with it. You commit frequently, one small scope diff at a time. Push to main once a full batch of work is complete and verified. Leftover must be…
spec-driven-tdd AGENTS.md
Instructions for strelov1/spec-driven-tdd: This repo is a skill-pack. When implementing an OpenSpec change, invoke the spec-driven-tdd skill and follow its lifecycle: plan in OpenSpec, isolate in a worktree, implement each task via TDD → simplify → review, then finish + archive.
mcp-repo-onboarding AGENTS.md
Instructions for rogermt/mcp-repo-onboarding, covering agents.md — agent & copilot instructions, current status, output verification, project identity and ⚠️ critical: tdd required.
arxiv-agent-mcp AGENTS.md
AGENTS.md instructions for tbaraniuk/arxiv-agent-mcp, covering agents.md, roles, test-writer, implementer and per-task loop.
think CLAUDE.md
Instructions for matiasvillaverde/think, covering claude.md, quick reference, hierarchical documentation, development philosophy and test-driven development (tdd).
opencode-copilot-instructions AGENTS.md
AGENTS.md instructions for ekroon/opencode-copilot-instructions, covering agent instructions, orchestration pattern, 1. always orchestrate (unless being orchestrated), 2. test-driven development (tdd) and tdd workflow for each module.