Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/yusufalikync/ccs/test-statusline)<a href="https://agentmods.dev/skills/yusufalikync/ccs/test-statusline"><img src="https://agentmods.dev/badge/skills/yusufalikync/ccs/test-statusline.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.1 | $0.00015 | $0.00498 |
| Opus 5 | $0.00008 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
test-statusline 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 7d 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
Test statusline.js
Run scripts/statusline.js with mock JSON input to verify output formatting and color-coded progress bars.
Instructions
Based on $ARGUMENTS, pick one of these test scenarios:
low — Low usage (all green)
echo '{"model":{"display_name":"Claude Opus 4"},"cost":{"total_cost_usd":0.12},"context_window":{"used_percentage":25},"workspace":{"current_dir":"/Users/test/my-project"},"session_id":"test-low"}' | node scripts/statusline.js
medium — Medium usage (yellow zone)
echo '{"model":{"display_name":"Claude Sonnet 4.5"},"cost":{"total_cost_usd":1.87},"context_window":{"used_percentage":75},"workspace":{"current_dir":"/Users/test/big-refactor"},"session_id":"test-medium"}' | node scripts/statusline.js
high — High usage (red zone)
echo '{"model":{"display_name":"Claude Opus 4"},"cost":{"total_cost_usd":5.42},"context_window":{"used_percentage":95},"workspace":{"current_dir":"/Users/test/marathon-session"},"session_id":"test-high"}' | node scripts/statusline.js
null — Null/missing values (fallback handling)
echo '{"model":{},"cost":{},"context_window":{},"workspace":{},"session_id":"test-null"}' | node scripts/statusline.js
No argument — Run all scenarios
If $ARGUMENTS is empty, run all four scenarios above sequentially and compare outputs.
Validation
After running, verify:
- Line 1 contains model name (or
?for null), folder name, and cost - Line 2 contains context progress bar with percentage
- No errors or crashes in stderr
- Null scenario shows safe fallbacks:
[?],$0.0000,0%
Report PASS/FAIL for each check.
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.
- 7d ago First seen · 50 lines · 15 tokens per session scan A 5fd1f637776c
test-statusline is a skill published in the GitHub repository yusufalikync/ccs (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 498 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-31.
Other skills, from other repositories
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.