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-research/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-research)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/aqe-research"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/aqe-research.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.00077 | $0.00380 |
| Opus 5 | $0.00039 | $0.00190 |
| Sonnet 5 | $0.00015 | $0.00076 |
| Haiku 4.5 | $0.00008 | $0.00038 |
Grade A, and why
aqe-research 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
Research AQE Systems
- Read
AGENTS.md, the question, and any user-supplied artifacts completely. - Define the decision the research must support, its scope, and freshness needs.
- Search local evidence broad-to-narrow with
rg --files,rg, code navigation, tests, configuration, documentation, and git history. - For current external claims, inspect primary sources: upstream repositories, releases, commits, issues, pull requests, and official documentation. Record dates, versions, commit identifiers, and links.
- Trace definitions to usages and public boundaries. Map dependencies, data flow, CLI/MCP parity, configuration generation, and tests when relevant.
- Classify each material statement using references/evidence-rules.md. Never repeat a benchmark, capability, or roadmap claim as fact without direct evidence.
- Synthesize only after gathering evidence. State contradictions, uncertainty, missing access, and stale documentation explicitly.
- Return:
- the decision-oriented summary;
- verified findings with source locations;
- inferences and their supporting evidence;
- gaps and risks;
- prioritized recommendations and the smallest useful next validation.
Use parallel agents only when the user requests delegation or repository instructions explicitly permit it. Treat Claude agent definitions as domain references; do not copy or execute their Claude-only hooks or 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.
- 8d ago First seen · 32 lines · 77 tokens per session scan A a73bb24333bd
aqe-research is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (475 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 380 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…