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/instructor-qanpx skills add cognesy/instructor-php --skill instructor-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.00065 | $0.01118 |
| Opus 5 | $0.00032 | $0.00559 |
| Sonnet 5 | $0.00013 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
instructor-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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructor QA
This skill is the repo-local quality assurance specialist for InstructorPHP. It chooses the smallest sufficient verification set for simple work, and for complex or multi-step QA it turns the work into a deterministic bd plan and executes it methodically.
Treat these files as source of truth:
QUALITY.mdfor verification lanes and command entrypointsCONTRIBUTING.mdfor contributor workflow expectationsAGENTS.mdfor repo-specific operating rules andbdusage.github/workflows/php.ymlfor the compatibility matrix.actrcfor localactdefaults
Read references/scenarios.md when you need the scenario-to-command mapping or the complex QA playbooks.
When To Use
Use this skill when the user asks to:
- run QA or decide which checks to run
- validate a feature, fix, refactor, dependency upgrade, or release candidate
- investigate a failing test, linter, docs QA run, or GitHub Actions workflow
- reproduce CI locally with
act - assess regression risk, production readiness, or verification gaps
- audit quality across multiple packages, layers, or tooling lanes
Working Model
Start by classifying the request into one or more QA lanes:
- behavior tests:
composer test,composer test-all, targeted Pest runs - integration and live-backend validation: telemetry interop and other opt-in suites
- static analysis: PHPStan, Psalm, dead-code, unused dependency checks
- structural and policy checks: Pint, Semgrep
- docs quality:
composer qa:docs, docs drift, andcomposer qa:docs-sitesfor deployable-site changes - dependency and compatibility validation: Composer resolution plus workflow matrix cells
- CI and workflow reproduction:
actagainst.github/workflows/php.yml - performance: PHPBench
Prefer the smallest sufficient lane set first. Expand only when the risk profile justifies it.
Default Execution Flow
- Read the request, changed files, and the relevant sections of
QUALITY.md. - Identify risk shape:
- local implementation
- docs/examples
- dependency or Composer manifest change
- workflow or CI change
- cross-package or release-sensitive change
- Choose the minimum verification bundle that can falsify the risky assumptions.
- Run checks from fast/high-signal to broader/slower.
- Separate failures caused by the current change from pre-existing repository debt.
- Report exactly what ran, what passed, what failed, what was skipped, and the residual risk.
What ships with it
2 files 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 · 109 lines · 65 tokens per session scan A d19ad86e578d
instructor-qa is a skill published in the GitHub repository cognesy/instructor-php (326 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 1,118 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-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-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-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.