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 skills add upex-galaxy/agentic-qa-boilerplate --skill iql-contextgit clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplateWrote 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/upex-galaxy/agentic-qa-boilerplate/iql-context)<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/iql-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/iql-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/iql-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/iql-context.svg" alt="Reviewed on agentmods" width="80" 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.00207 | $0.04618 |
| Opus 5.5 | $0.00083 | $0.01847 |
| Sonnet 5.5 | $0.00041 | $0.00924 |
| Haiku 4.5 | $0.00021 | $0.00462 |
Grade A, and why
iql-context 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iql-context
Kind
context(agentic-qa-core/references/skill-composition-strategy.md§2b). Shipped upstream and synced verbatim; a project adapts it through the two seams in §"How a project adapts it", never by editing this file.
Compact Rules
- DO: answer "why is the process shaped this way" from the index below, then point at the canonical reference for the procedure; never restate a DoD, a transition table or a link catalog that a reference already owns.
- DO: name stages by word (Shift-Left, Planning, Execution, Reporting, Documentation, Automation, Regression, Observation), never by number; a numbered "Stage N" in an older doc resolves through
agentic-qa-core/references/stage-gates.md. - DO: read
.agents/project.yaml→qa.methodologybefore saying which stages a project runs or how strict its gates are; the shipped values are a default, not a decision. - DO: read
references/project-overrides.mdfor the project's own rules and exceptions; they win over this index for THAT project, and only there. - DO NOT: resolve a web-vs-repo disagreement on your own. The repo's executable doctrine (
agentic-qa-core/references/*) is what the skills enforce; the website is the public narrative. State both readings and cite both. - DO NOT: treat this skill as SUT knowledge. Entities, endpoints, infra and Jira content live in
.context/maps and the project's<aspect>-contextskills. - DO NOT: edit this SKILL.md or its synced references in a consumer project; propose a refinement per
agentic-qa-core/references/skill-refinement-protocol.md(project-owned prose goes inreferences/project-overrides.md). - WHEN a question is about ONE aspect (phases and steps, the agentic contract, the eight approaches, the thirteen invariants): load only that reference from §"References".
Read full SKILL.md when: building a briefing that must explain the methodology to a subagent, answering "why" questions about the ladder or the stages, or checking which invariant a proposed shortcut violates.
What ships with it
7 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.
- 5d ago Changed 5e9a05ac787c
- 12d ago Changed 8e1ec647de5d
- 22d ago First seen · 127 lines · 207 tokens per session scan A ac8102cb660b
iql-context is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 4d ago), licensed MIT. It adds 207 tokens to every session and 4,618 once invoked, about $0.0008 per session on Opus 5.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-09-25.
Other skills, from other repositories
agent-testing-harness
Use this skill when testing AI agent systems. Activate when the user needs to test agent behavior, write tests for multi-agent systems, implement agent evaluation frameworks, create test harnesses for autonomous agents, or validate agent outputs systematically.
api-test-patterns
Write comprehensive API tests for REST and GraphQL endpoints. Use this skill when testing APIs, writing contract tests, or validating integrations. Activate when: api testing, REST test, GraphQL test, endpoint testing, integration test, postman, contract testing.
test-generation-patterns
Use this skill when generating tests with AI assistance. Activate when the user wants to create unit tests, integration tests, generate test cases, improve test coverage, write tests for existing code, or set up testing patterns for their project.
playwright-patterns
Write reliable, maintainable E2E tests with Playwright best practices. Use this skill when writing Playwright tests, debugging flaky tests, or setting up E2E automation. Activate when: playwright, e2e test, end-to-end, browser testing, UI automation, web testing.
test-case-design
Design comprehensive test cases with proper coverage and clear documentation. Use this skill when writing test cases, creating test suites, or improving test coverage. Activate when: test case, test scenario, test coverage, test design, write tests, BDD, gherkin.
skill-testing
Test skills for correct activation, content quality, and regression — both automated checks (frontmatter validity, lint) and manual verification (query-suite activation testing). Covers CI integration and how to catch skill regressions before users do. Use this skill when adding skills to a repo, setting up CI for a…