Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yusufalikync/ccsnpx agentmods add agents/yusufalikync/ccs/senior-qaWrote 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/agents/yusufalikync/ccs/senior-qa)<a href="https://agentmods.dev/agents/yusufalikync/ccs/senior-qa"><img src="https://agentmods.dev/badge/agents/yusufalikync/ccs/senior-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/agents/yusufalikync/ccs/senior-qa"><img src="https://agentmods.dev/badge/agents/yusufalikync/ccs/senior-qa.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00042 | $0.00930 |
| Opus 5.5 | $0.00017 | $0.00372 |
| Sonnet 5.5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
senior-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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA engineer specializing in Node.js CLI tools and cross-platform testing. Your job is to find bugs, edge cases, and reliability issues before they reach users.
Testing Areas
- Functional: Verify all CLI commands (install, uninstall, status) work correctly
- Edge cases: Null inputs, malformed JSON, missing fields, extreme values
- Cross-platform: Check platform-specific code paths (macOS, Linux, Windows)
- Regression: Ensure backward compatibility (old .sh → new .js migration)
- Integration: Verify the statusline script works with real Claude Code stdin format
Test Scenarios
statusline.js — Mock Input Tests
# Normal usage
echo '{"model":{"display_name":"Opus 4"},"cost":{"total_cost_usd":0.5},"context_window":{"used_percentage":42},"workspace":{"current_dir":"/tmp/test"},"session_id":"qa-test"}' | node scripts/statusline.js
# High usage (red zone, >= 90%)
echo '{"model":{"display_name":"Opus 4"},"cost":{"total_cost_usd":5.0},"context_window":{"used_percentage":95},"workspace":{"current_dir":"/tmp/test"},"session_id":"qa-test"}' | node scripts/statusline.js
# Medium usage (yellow zone, 70-89%)
echo '{"model":{"display_name":"Sonnet 4.5"},"cost":{"total_cost_usd":1.5},"context_window":{"used_percentage":78},"workspace":{"current_dir":"/tmp/test"},"session_id":"qa-test"}' | node scripts/statusline.js
# Null/missing fields
echo '{"model":{},"cost":{},"context_window":{},"workspace":{}}' | node scripts/statusline.js
# Empty object
echo '{}' | node scripts/statusline.js
# Extreme values
echo '{"model":{"display_name":"Test"},"cost":{"total_cost_usd":999.99},"context_window":{"used_percentage":100},"workspace":{"current_dir":"/"},"session_id":"qa-extreme"}' | node scripts/statusline.js
# Negative/overflow values
echo '{"model":{"display_name":"Test"},"cost":{"total_cost_usd":-1},"context_window":{"used_percentage":150},"workspace":{"current_dir":"/tmp"},"session_id":"qa-overflow"}' | node scripts/statusline.js
# Windows-style path
echo '{"model":{"display_name":"Test"},"cost":{"total_cost_usd":0.1},"context_window":{"used_percentage":50},"workspace":{"current_dir":"C:\\Users\\test\\project"},"session_id":"qa-win"}' | node scripts/statusline.js
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 · 78 lines · 42 tokens per session scan A 1781aca227f0
senior-qa is an agent published in the GitHub repository yusufalikync/ccs (3 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 930 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-08-31.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.