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/proffesor-for-testing/agentic-qe/aqe-plan-worknpx skills add proffesor-for-testing/agentic-qe --skill aqe-plan-workgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/aqe-plan-work)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/aqe-plan-work"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/aqe-plan-work.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.1 | $0.00083 | $0.00404 |
| Opus 5 | $0.00042 | $0.00202 |
| Sonnet 5 | $0.00017 | $0.00081 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
aqe-plan-work 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 6d 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
Plan AQE Work
- Read
AGENTS.md, the objective, relevant research, affected implementation, tests, configuration, and public boundaries. - Define observable outcomes, non-goals, constraints, assumptions, and decisions that require human approval.
- Decompose work into independently verifiable deliverables. Map dependencies, consumers, migrations, compatibility boundaries, and rollback points.
- Select the smallest useful specialist fleet with references/planning-framework.md. Give every selected specialty a concrete output; do not summon the whole fleet.
- Arrange phases so contracts, safety controls, and durable tests precede or accompany implementation. Check CLI/MCP and Claude/Codex parity when shared capabilities cross those surfaces.
- Identify work that can run in parallel and a clear critical path. Do not use unsupported precision for time estimates; size work by risk and dependency.
- Attach acceptance criteria and the narrowest verification command to each deliverable. Include security, resilience, performance, accessibility, or data-integrity gates only when triggered by the actual scope.
- End with prioritized milestones, risks and mitigations, open decisions, and a recommended first vertical slice.
Use Ruflo for persistent memory, learned routing, hooks, or multi-agent coordination only when its operational benefit exceeds its setup overhead. Treat Claude agent definitions as domain references; translate their workflows into available Codex actions rather than copying Claude-only tool syntax.
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.
- 6d ago First seen · 32 lines · 83 tokens per session scan A bd76c97cd217
aqe-plan-work is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (474 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 404 once invoked, about $0.0004 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
gh-bulk-issues
Orchestrate parallel Mastra Code headless instances to debug and fix multiple GitHub issues simultaneously.
qa-investigation
Investigate a specific test failure to its root cause and document the why. Detects whether a failing test is flaky (intermittent) or a deterministic bug during reproduction. Use when a test fails and you need the real cause, not just to make it green. Execution layer, not strategy review. Keywords: flaky test…