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 skills add cognesy/instructor-php --skill examples-qagit clone --depth 1 https://github.com/cognesy/instructor-phpWrote 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/skills/cognesy/instructor-php/examples-qa)<a href="https://agentmods.dev/skills/cognesy/instructor-php/examples-qa"><img src="https://agentmods.dev/badge/skills/cognesy/instructor-php/examples-qa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cognesy/instructor-php/examples-qa"><img src="https://agentmods.dev/badge/skills/cognesy/instructor-php/examples-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00067 | $0.02751 |
| Opus 5.5 | $0.00027 | $0.01100 |
| Sonnet 5.5 | $0.00013 | $0.00550 |
| Haiku 4.5 | $0.00007 | $0.00275 |
Grade A, and why
examples-qa 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 1mo 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructor examples QA
Use the examples suite as an end-to-end check of Instructor behavior, but keep the execution mode explicit. A live run tests provider and transport integration; a record run creates reusable HTTP fixtures; a replay run tests the current code against fixed provider responses without spending tokens or contacting a network.
Inspect before running
Run commands from the repository root. Discover the target and its canonical selector first:
php bin/instructor-hub list
php bin/instructor-hub show getters_and_setters
The hub accepts a front-matter docname, numeric index, short ID such as xe4bb,
or example path. Read the target's run.php before diagnosing it. Check its tags
and whether it builds an HTTP client implicitly or supplies a custom client/mock.
Treat these sources as authoritative when the prose documentation differs:
just/examples.just— preferred record/replay command wrappersexamples/boot.phpandexamples/_support/HttpRecordingBoot.php— mode and recording-directory behaviorpackages/hub/src/Commands/EnhancedRunAllExamples.php— corpus filtering andOK/ASSERT/ERROR/FLAKYclassificationpackages/hub/src/Services/ExampleRepository.php— selector resolutionQUALITY.md— repository QA policy and operational caveats
Choose the execution mode
Use the smallest mode that answers the question:
| Mode | Command shape | What it proves |
|---|---|---|
| pass | INSTRUCTOR_EXAMPLES_HTTP=pass ... or no mode |
Normal behavior; no record/replay middleware is attached. LLM examples use the live provider. |
| record | just examples-record <selector> |
Live provider call succeeds and the response can be persisted as a sanitized cassette. |
| replay | just examples-replay <selector> |
Current code consumes the fixed response correctly, with no network or provider credentials required. |
Run without record/replay
Use pass mode for a normal baseline or a live provider smoke check:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 296 lines · 67 tokens per session scan A e67f2eac45c6
examples-qa is a skill published in the GitHub repository cognesy/instructor-php (328 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 2,751 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
error-analysis
Evals-first error analysis for LLM apps: clusters real Langfuse or JSONL traces into a human-confirmed failure taxonomy with counts, then recommends binary pass/fail evals for recurring named modes. Use to learn what to measure before writing evals. Not for CI failures.
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.