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/floomhq/moto/qanpx skills add floomhq/moto --skill qagit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/qa)<a href="https://agentmods.dev/skills/floomhq/moto/qa"><img src="https://agentmods.dev/badge/skills/floomhq/moto/qa.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00502 |
| Opus 5 | $0.00030 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
qa 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 4d 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
QA Skill
Step 1: Get the diff
git diff main...HEAD
# or for staged changes:
git diff --cached
# or for a specific commit range:
git diff <from>..<to>
Step 2: Categorize changes
For each changed file, identify:
- Type: frontend / backend / config / tests / docs / infra
- Scope: which feature/module/route is affected
- Risk: low / medium / high
Step 3: Impact analysis
Frontend changes
- Which pages/routes render the changed components?
- Are there loading/error states to test?
- Are there mobile/desktop variants to check?
- Does the change affect layout shift or performance?
Backend changes
- Which API endpoints are affected?
- Which consumers call those endpoints?
- Are there database queries that changed?
- Are there cron jobs or background tasks affected?
Config/env changes
- Which environments are affected?
- Is there a migration or deployment step needed?
- Are there secrets that need to be rotated or updated?
Breaking changes
- Are any public interfaces changing signature?
- Are any database schemas changing?
- Are any API contracts changing?
Step 4: Test plan
Generate a concrete test checklist based on the affected areas:
TEST PLAN for this diff:
Pages/routes to verify:
- [ ] /path/to/page - verify [specific behavior]
- [ ] /other/route - verify [specific behavior]
API endpoints to verify:
- [ ] GET /api/endpoint - verify [expected response]
Edge cases to check:
- [ ] [specific edge case]
- [ ] [error state]
Regression checks (ensure nothing broke):
- [ ] [existing feature that could be affected]
Step 5: Risk summary
QA SUMMARY
Files changed: N
Risk level: [LOW / MEDIUM / HIGH]
Affected areas: [list]
Manual testing required: [YES / NO]
Recommended: [SHIP / NEEDS MORE TESTING / STOP]
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.
- 4d ago First seen · 85 lines · 61 tokens per session scan A 7b54657ce743
qa is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 502 once invoked, about $0.0003 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.