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 agentmods add skills/awrshift/agent-memory-kit/qa-sweepnpx skills add awrshift/agent-memory-kit --skill qa-sweepgit clone --depth 1 https://github.com/awrshift/agent-memory-kitWhat 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 | $0.00199 | $0.00792 |
| Opus 5 | $0.00100 | $0.00396 |
| Sonnet 5 | $0.00040 | $0.00158 |
| Haiku 4.5 | $0.00020 | $0.00079 |
Grade A, and why
qa-sweep scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
ux-critique. Non-browser: contract (curl) · honesty (curl + read-only store queries). This is a copy
100% identical to qa-sweep — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Sweep — multi-lens agent QA of the live product
Read projects/<name>/qa/README.md FIRST (the protocol SSOT: environment rules · the five lens briefs ·
findings format · triage) — the lens briefs in agent prompts come verbatim from there, and the
account/mutation policy it sets is a hard rail, not advice. If that file doesn't exist yet,
create it from the layer's protocol template (${CLAUDE_PLUGIN_ROOT}/reference/qa-PROTOCOL-TEMPLATE.md in
the kit repo — copy it from there if this project only adopted the layer's .claude/ files)
and fill the placeholders before sweeping.
Steps
- Preflight (integrator, by hand): bring up the stack the protocol names (app · API · store) · pick the account per the protocol's policy (the demo/real account = OBSERVE-ONLY always; the seeded sacrificial account = mutation QA only when the run brief grants it) · make sure nothing else is writing to the shared store during the sweep (no integration test suites, no live jobs).
- Pick lenses for this run (default: user-flow + contract in parallel, then edge-state, then honesty + ux-critique). Browser lenses run CONCURRENTLY via the isolated Playwright MCP servers the protocol lists (one server per concurrent browser agent — mechanism + logged-in seed recipe in the protocol § Parallel lenses). Browser lenses: user-flow · edge-state · ux-critique. Non-browser: contract (curl) · honesty (curl + read-only store queries).
- Spawn
qaagents with the lens brief from the protocol § Lens briefs + the run scope (which screens/flows changed recently — QA the delta first, then one broad pass). - Verify before ticketing (the fact-check rule): reproduce every P1/P2 finding yourself (the named repro steps) before it becomes a ticket. Unreproducible → back to the agent or drop with a note. «Impressions» never become tickets directly.
- Land the results: verified findings → backlog tickets (P1/P2) or a minors batch (P3) ·
one run record
projects/<name>/qa/qa-run-YYYYMMDD.md(lenses run · coverage · findings table with verified/dropped status · pointers to tickets) · a row in the protocol's § Runs index. - Cleanup: stop dev servers, remove stray screenshots from the repo root, re-seed the sacrificial account if a mutation run dirtied it.
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.
- yesterday First seen · 46 lines · 199 tokens per session scan A 7fce5b08c9c0
qa-sweep is a skill published in the GitHub repository awrshift/agent-memory-kit (31 stars, last pushed yesterday), licensed MIT. It adds 199 tokens to every session and 792 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to qa-sweep, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
kungfu-agent-onboarding
Discover the exact Kungfu Project, WorkConsole, WorkRef, Skill catalog, and Core Work state admitted to this Amp process.
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
bridge-sync
End-of-sprint batch-sync: pushes ALL pending scope:core + scope:org commits from the local user branch to BOTH upstreams (open-bridge + your org overlay) in one operation, with per-destination scrubbing and parallel PR creation. Complements /promote (per-commit) and /contribute (per-file) with a sprint-level workflow.…
briefing
Assembles a session context briefing from your configured issue tracker, recent git history, and active work signals. Use when: starting a new session, resuming after a break, user says 'catch me up', 'what was I working on', 'where did I leave off', context recovery after compaction, or user asks for project…
mcaf-agile-delivery
Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.