Borrowing it
Nothing to install: this file belongs to arnaudgelas/K-Ops. 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/arnaudgelas/K-Ops/main/.claude/skills/qa-agent/SKILL.mdgit clone --depth 1 https://github.com/arnaudgelas/K-OpsWrote 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/arnaudgelas/k-ops/qa-agent)<a href="https://agentmods.dev/skills/arnaudgelas/k-ops/qa-agent"><img src="https://agentmods.dev/badge/skills/arnaudgelas/k-ops/qa-agent/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/arnaudgelas/k-ops/qa-agent"><img src="https://agentmods.dev/badge/skills/arnaudgelas/k-ops/qa-agent.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.00019 | $0.00818 |
| Opus 5.5 | $0.00008 | $0.00327 |
| Sonnet 5.5 | $0.00004 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
qa-agent 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Q&A Agent
Goal
Produce useful answers without letting knowledge disappear into chat.
Workflow
- Read
notes/Home.mdornotes/Indexes/Flat_Concept_Index.md, and runsearch_vault.pyprogrammatically. - Classify the query using
notes/Runbooks/Query_Planner.md(one of:lookup,synthesis,contradiction,freshness,code,audit,research). - Execute the required retrieval layers in the order specified for that query class.
- Find the most relevant concept pages and source summaries (capped at reading at most 10 concept pages total).
- Answer from the vault.
- Save the answer memo in
notes/Answers/YYYYMMDDTHHMMSS-topic.mdusing the schema below. - File durable improvements back into concept pages, open questions, contradictions, or TODOs.
Answer Memo Schema
Frontmatter:
title(Human-readable topic title)type: answerasked_at(ISO-8601 date)answer_quality(must be exactlydurableif updating the vault, ormemo-onlyif not)scope(must be exactlysharedfor durable answers, orprivatefor memo-only answers)query_class(must be one of:lookup,synthesis,contradiction,freshness,code,audit,research)sources_consulted(YAML list of everysource_idopened during the session)retrieval_path(YAML list of dictionaries specifying each retrieval step taken; each step must have keys:method,layer,query,results_count)fetch_required(boolean, indicating whether external web fetching was performed/required)tags(must includekb/answer)
Structure:
- Must have a top-level heading (e.g.
# Question/# Answer). - Must have a second-level heading (e.g.
## Summary,## Analysis). - Must have a
## Vault Updatessection.- If
answer_quality: durable, this section must list the exact edits made to concept pages. - If
answer_quality: memo-only, this section must be exactly- None..
- If
Rules
- Prefer vault-grounded answers.
- State uncertainty clearly (e.g., "according to [[Sources/...]]" vs "this is unclear").
- Do not fabricate evidence.
- Every factual claim in the answer must carry an inline wikilink citation:
[[Sources/<source_id>|<source_id>]]or[[Concepts/<name>|<name>]]. If no source supports a claim, mark it(unverified). - For a consequential answer, gate the evidence by stakes: run
consequence-gate --tier <recommendation|decision|autonomous>(optionally--concept <stem>). Do not let blocked, quarantined, or unsupported claims back a high-consequence answer; flag the shortfall in the memo instead.
What ships with it
1 file 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.
- 1mo ago First seen · 54 lines · 19 tokens per session scan A cadf69d4b8d7
qa-agent is a skill published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 818 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
kb-lint
Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-export
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
wiki-query
Search and synthesize answers from the compiled Obsidian wiki, including cited and multi-hop answers. Use for questions about existing wiki knowledge or fast index-only lookups, and for challenge requests ("challenge this", "argue against X", "poke holes in my plan") that look for the vault's own evidence against a…