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 skills add sampleXbro/agentsmesh --skill senior-manual-qagit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/senior-manual-qa)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/senior-manual-qa"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/senior-manual-qa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/senior-manual-qa"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/senior-manual-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00059 | $0.02482 |
| Opus 5.5 | $0.00024 | $0.00993 |
| Sonnet 5.5 | $0.00012 | $0.00496 |
| Haiku 4.5 | $0.00006 | $0.00248 |
Grade A, and why
senior-manual-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 1mo 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Senior Manual QA
Run this skill when a user asks to:
- "test the library completely"
- "create a test plan"
- "validate all edge cases"
- "do senior manual QA"
- "check release readiness"
This skill is for QA execution and reporting. It does not require code changes.
Mandatory output: create a QA report markdown file in the repository.
Core Principles
- Test behavior, not assumptions.
- Prioritize business-critical flows first.
- Record evidence for every pass/fail claim.
- Keep tests deterministic and reproducible.
- Use isolated temp workspaces for destructive scenarios.
- Never claim completion while blockers remain.
Phase 1: Build the Test Plan
Create a concise plan before running commands.
Include:
- Scope (what is in/out).
- Entry criteria (buildable state, dependencies installed).
- Exit criteria (all required gates complete, blocker count).
- Risk areas and priority order.
- Test matrix (happy path, boundaries, invalid input, recovery, regression).
- Environment details (OS, shell, Node/package manager).
Phase 2: Baseline and Environment Checks
Capture baseline details:
- Current git status (clean or dirty).
- Node and package manager versions.
- Install state (
pnpm installonly if needed). - Existing warnings that are known/non-blocking.
If a command mutates generated artifacts during tests, restore workspace state unless the user asked to keep changes.
Phase 3: Quality Gate Execution
Run gates in this order unless the user overrides:
pnpm typecheckpnpm lintpnpm buildpnpm testpnpm test:e2e(if available)pnpm test:coverage(if available)pnpm audit --audit-level=high
For each gate, record:
- command
- exit code
- duration (if available)
- key output lines
Phase 4: Manual Edge-Case Matrix (CLI + Library)
Use isolated temp directories for manual CLI cases. Validate both exit code and message clarity.
Minimum matrix:
- Command discovery:
--help--version- unknown command
- Required input validation:
- missing config
- missing required args
- invalid option value
- Lifecycle flow:
- init/setup
- successful primary command flow
- check/verify flow
- Drift/conflict behavior:
- modify canonical input and re-check
- confirm conflict output is actionable
- Install/import flow (if applicable):
- happy path
- no-op/sync with no manifest
- invalid source path/format
- Error resilience:
- malformed file (YAML/JSON/markdown frontmatter)
- unsupported target/feature
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.
- 1mo ago First seen · 286 lines · 59 tokens per session scan A 373bf120b679
senior-manual-qa is a skill published in the GitHub repository sampleXbro/agentsmesh (26 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,482 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
update-package-skill
Updates an existing package Skill for a new release of its npm or local package by testing only what changed since the version the Skill names. Use when a maintainer asks to refresh a package Skill after a release, or when a SKILL.md names an older tested version than the package.
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…
subagent-driven-development
Orchestrating sub-agents through TDD phases for complex features.
test-driven-development
Red-green-refactor TDD implementation cycle.