qa-list

A command that lists saved question-and-answer documents from the project's docs/qa/ directory, optionally grouped by a category such as math, web, or statistics.

In plain words
What is it for?
Use it to display all saved Q&A documents or filter the list by category with /qa-list [category].
Why use it?
It makes existing Q&A records easier to find without opening files one by one. It also shows category counts and gives a clear message when no matching documents exist.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/roboco-io/plugins/qa-list
Any agent
npx skills add roboco-io/plugins --skill qa-list
Clone the repo
git clone --depth 1 https://github.com/roboco-io/plugins

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00504
Opus 5 $0.00015 $0.00252
Sonnet 5 $0.00006 $0.00101
Haiku 4.5 $0.00003 $0.00050

Measured 2d ago against content hash 33cb78997e7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

qa-list 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 2d 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.

plugins/documentation/skills/qa-list/SKILL.md · 69 lines

What it actually says

Q&A List Skill

저장된 Q&A 문서 목록을 표시합니다.

사용법

/qa-list [카테고리]

옵션

  • 카테고리 미지정: 전체 목록 표시
  • 카테고리 지정: 해당 카테고리만 필터링

카테고리

math, topology, algebra, geometry, ml, statistics, cs, web, infra, general

동작

  1. docs/qa/ 디렉토리 스캔
  2. 각 파일의 frontmatter에서 메타데이터 추출
  3. 테이블 형태로 목록 표시
  4. 카테고리별 통계 출력

출력 형식

## Q&A 목록

총 N개의 Q&A가 저장되어 있습니다.

| # | 날짜 | 카테고리 | 질문 | 파일 |
|---|------|----------|------|------|
| 1 | 2026-01-18 | topology | Persistent Homology가 뭐야? | 20260118-143052-persistent-homology.md |
| 2 | 2026-01-18 | algebra | Tensor Train 분해란? | 20260118-150023-tensor-train.md |
...

### 카테고리별 통계

| 카테고리 | 개수 |
|----------|------|
| topology | 5 |
| algebra | 3 |
| ml | 2 |

실행 절차

  1. docs/qa/ 디렉토리 존재 확인
  2. 파일 목록 수집
  3. 각 파일의 frontmatter 파싱
  4. 카테고리 필터 적용 (지정된 경우)
  5. 테이블 형식으로 출력
  6. 카테고리별 통계 출력

에러 처리

  • docs/qa/ 디렉토리가 없으면: "Q&A 문서가 없습니다. /qa 명령어로 먼저 Q&A를 생성하세요."
  • 지정한 카테고리에 문서가 없으면: "해당 카테고리의 Q&A가 없습니다."

필터: $ARGUMENTS

Changes

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.

  1. 2d ago First seen · 69 lines · 29 tokens per session scan A 33cb78997e7e

Subscribe to this mod's changes

qa-list is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 504 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens