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/vscarpenter/gsd-task-manager/source-command-qchecknpx skills add vscarpenter/gsd-task-manager --skill source-command-qcheckgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWhat 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.00024 | $0.00540 |
| Opus 5 | $0.00012 | $0.00270 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
source-command-qcheck 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.
How it starts
The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-qcheck
Use this skill when the user asks to run the migrated source command qcheck.
Command Template
Review all changed files in this session as a skeptical staff engineer for the gsd-taskmanager codebase. Apply the full coding-standards.md and AGENTS.md rules.
Run git status and git diff first to see what has changed. Then evaluate each changed file against:
- Standards compliance — Files ≤350 lines, functions ≤30 lines, ≤3 nesting levels, no magic numbers, descriptive naming.
- Type safety — All function signatures typed, no
anywithout justification, Zod validation at boundaries (user input, import, MCP tool inputs). - TDD evidence — Were tests written first? Check git log if uncertain. Each new behavior should have a behavior-named test.
- Test quality — Positive AND negative cases. Coverage ≥80% for changed files. Independent tests (no shared mutable state). Mocks at boundaries, not deep.
- Error handling — Typed errors, no swallowed exceptions,
toast.error()from sonner instead ofwindow.alert(). - Project-specific gotchas:
- PocketBase:
client_updated_at(notupdated) in sort/filter,_superusersadmin endpoint, 100ms push throttle, batch lookups not N+1. - Schema:
.safeParse()(not.parse()) on user input paths; import uses.strip(), export uses.strict(). - Tests:
bun run test(notbun test);localStorage.removeItem(key)(notclear()). - UI:
toast.error()(notalert()); accessibility baseline from coding-standards Part 2.
- PocketBase:
- Security — Input validation, no committed secrets, parameterized queries, least privilege.
- Observability — Structured logging via
lib/logger.ts, noconsole.*in production paths, no PII in logs. - Definition of Done — Every box in coding-standards.md Part 7 "Definition of Done" checklist.
Distinguish blocking issues from suggestions. Prefix non-blocking comments with nit: or suggestion:.
Do not rewrite the code. Return a structured list of findings, organized by file, with file:line — issue — fix.
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.
- 2d ago First seen · 33 lines · 24 tokens per session scan A 2b61b38a2657
source-command-qcheck is a skill published in the GitHub repository vscarpenter/gsd-task-manager (24 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 540 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.
Other skills, from other repositories
lastest
Run visual regression tests, review screenshot diffs, and manage baselines on a Lastest instance via the @lastest/mcp-server MCP tools.
lastest
Lastest is a visual regression testing platform. It records browser tests, runs them via Playwright, diffs screenshots, and uses AI to classify changes. Available as an MCP server for AI agent integration.
Lastest design system
Visual + content rules for Lastest, the free open-source visual regression testing platform. Anchored on the Delta Mark logo + 5-stop split-complementary palette.
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
compare
Structured comparison of 2+ alternatives with consistent criteria and decision matrix.
fix-reported-issue
Triage and fix the oldest unresolved issue from the production issuereports table. Use this skill whenever the user asks to check for reported issues, fix a reported bug, address user feedback, work on issue reports, or triage production issues. Also use when the user says things like "check prod for issues", "any new…