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/samplexbro/agentsmesh/post-feature-qanpx skills add sampleXbro/agentsmesh --skill post-feature-qagit clone --depth 1 https://github.com/sampleXbro/agentsmeshWhat 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.00078 | $0.01090 |
| Opus 5 | $0.00039 | $0.00545 |
| Sonnet 5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
post-feature-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 3d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Post-Feature QA — Senior QA Engineer Mode
When a feature, story, or task has been implemented, you MUST run this QA pass before marking it complete. Acting as a senior QA engineer, verify test coverage and story alignment. Never claim work is done without this review.
When to Trigger
- You just finished implementing a story or task
- You completed a feature and are about to commit or open a PR
- The user says "feature is done", "story complete", or "ready for review"
- You are about to mark checklist items complete in
tasks/todo.mdor similar - Before any "verification complete" or "acceptance criteria verified" claim
Core Workflow
1. Load the Story/Spec
- Find the story or feature spec. Common locations:
ruleforge-prd.md(or similar PRD)tasks/todo.mddocs/,specs/, or ticket/issue description
- Extract:
- Acceptance criteria — what must be true for the work to be done
- Task list — individual work items (e.g. 2.1.1, 2.1.2)
- Explicit test requirements — e.g. "Write tests: valid, invalid, every field type"
2. Cross-Check Acceptance Criteria
For each acceptance criterion:
| Criterion | Action |
|---|---|
| Behavioral | Verify a test exists that asserts the behavior |
| Config/format | Verify tests for valid + invalid inputs |
| Error handling | Verify tests for error paths and error messages |
| Edge cases | Empty, null, boundary values, invalid types |
If any criterion has no corresponding test, add the test.
3. Edge Case Checklist
Load ./references/edge-case-checklist.md for a full reference. For every public API, config schema, or behavior:
- Valid inputs: minimal valid, full valid, optional fields omitted
- Invalid types: wrong type (string vs number, array vs object, etc.)
- Boundaries: empty array/string, single element, max length if applicable
- Null/undefined: missing required fields, explicit null where relevant
- Invalid values: out-of-range, invalid enum, malformed structure
- Combined failures: multiple invalid fields in one input
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.
- 3d ago First seen · 119 lines · 78 tokens per session scan A b70fa378e25d
post-feature-qa is a skill published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 1,090 once invoked, about $0.0004 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
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
setup
This skill should be used when user encounters "Azure MCP error", "Azure authentication failed", "az login required", "Azure CLI not found", or needs help configuring Azure MCP integration.
mongodb-natural-language-querying
Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents. Use this skill whenever the user asks to write, create, or generate MongoDB queries, wants to filter/query/aggregate data in MongoDB, asks "how do I query...", needs help with…