Borrowing it
Nothing to install: this file belongs to proffesor-for-testing/agentic-qe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/proffesor-for-testing/agentic-qe/main/.agents/skills/aqe-plan-quality/SKILL.mdgit 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-quality)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/aqe-plan-quality"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/aqe-plan-quality.svg" alt="Measured on agentmods" 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.00073 | $0.00293 |
| Opus 5 | $0.00036 | $0.00147 |
| Sonnet 5 | $0.00015 | $0.00059 |
| Haiku 4.5 | $0.00007 | $0.00029 |
Grade A, and why
aqe-plan-quality 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 8d 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 Quality
- Read
AGENTS.md, the requested change, and the affected public boundaries. - Inspect the closest implementation and tests before proposing work.
- Classify the risk domains using references/qe-routing.md.
- Select only the QE specialties needed. Treat Claude agent definitions as
domain references; do not copy their Claude-only
Task,SendMessage, or hook syntax into Codex actions. - Produce a plan that covers:
- observable requirements and acceptance criteria;
- affected boundaries, dependencies, and failure modes;
- durable tests first, then implementation-coupled tests;
- security, performance, accessibility, contract, or resilience checks when triggered by the change;
- the narrowest repository verification commands.
- Flag assumptions, unavailable environments, destructive operations, and decisions requiring human approval.
Prefer evidence from repository code and configuration over generic test checklists. Keep the selected fleet small and explain each specialty’s purpose.
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.
- 8d ago First seen · 26 lines · 73 tokens per session scan A 96fd62505b98
aqe-plan-quality is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (475 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 293 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
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
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…