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 skills/cognesy/instructor-php/examples-qanpx skills add cognesy/instructor-php --skill examples-qagit clone --depth 1 https://github.com/cognesy/instructor-phpWhat 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.00067 | $0.02751 |
| Opus 5 | $0.00034 | $0.01375 |
| Sonnet 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 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.
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.
- 2d 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 (326 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 2,751 once invoked, about $0.0003 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 skills, from other repositories
lab-creator
Guide for creating new AI Gateway labs. Use when users want to create a new lab in the labs/ folder. This skill provides the standard lab structure, templates, and patterns used across the AI Gateway repository including Jupyter notebooks, Bicep infrastructure templates, APIM policies, and README documentation.
apim-bicep
Guide for building Bicep files for Azure API Management (APIM) and related Azure services. Use when users want to create, modify, or understand Bicep templates for APIM instances, APIs, backends, subscriptions, policies, products, loggers, diagnostics, and MCP servers. This skill provides Bicep syntax, patterns from…
apim-terraform
Guide for creating Terraform files for Azure API Management (APIM) and related Azure services. Use when users want to create, modify, or understand Terraform configurations for APIM instances, APIs, backends, subscriptions, policies, products, loggers, diagnostics, and supporting infrastructure using the azurerm…
apim-kql
Guide for creating Kusto Query Language (KQL) queries for Azure API Management tables in Azure Monitor (Log Analytics Workspace). Use when users want to query, analyze, or monitor APIM logs including gateway logs, LLM/AI logs, MCP logs, WebSocket logs, and Application Insights data. This skill provides KQL syntax…
apim-policies
Guide for creating Azure API Management (APIM) XML policies. Use when users want to create, modify, or understand APIM policies including inbound/outbound processing, authentication, rate limiting, caching, transformations, AI gateway policies, and policy expressions. This skill provides policy syntax, examples, and…
presentation
Turn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.