Borrowing it
Nothing to install: this file belongs to hoangsonww/WealthWise-Finance-Tracker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoangsonww/WealthWise-Finance-Tracker/master/.agents/skills/test-coverage/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/WealthWise-Finance-TrackerWrote 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/hoangsonww/wealthwise-finance-tracker/test-coverage)<a href="https://agentmods.dev/skills/hoangsonww/wealthwise-finance-tracker/test-coverage"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/test-coverage/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/hoangsonww/wealthwise-finance-tracker/test-coverage"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/test-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 16 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 17 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00057 | $0.00417 |
| Opus 5 | $0.00028 | $0.00209 |
| Sonnet 5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
test-coverage 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 9d 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
Run the WealthWise test suite with coverage and summarize the results.
Scope
| Argument | Command |
|---|---|
| (none) | npm run test:coverage (all packages) |
api |
npx turbo test:coverage --filter=@wealthwise/api |
web |
npx turbo test:coverage --filter=@wealthwise/web |
types or shared-types |
npx turbo test:coverage --filter=@wealthwise/shared-types |
Note: API tests use mongodb-memory-server with a 30-second startup. Do not reduce the timeout.
Steps
- Run the appropriate coverage command
- Parse the output and report:
Package Tests Pass Fail Stmts Branch Funcs Lines
@wealthwise/api 138 138 0 XX% XX% XX% XX%
@wealthwise/web 41 41 0 XX% XX% XX% XX%
@wealthwise/shared-types 151 151 0 XX% XX% XX% XX%
─────────────────────────────────────────────────────────────────────────────
Total 330 330 0
- Flag any file with < 80% branch coverage as needing attention.
- If tests fail, show the full error for each failing test (file path, test name, error message).
- Do NOT attempt to fix failing tests unless explicitly asked.
Baseline
The expected passing count is 330 tests (138 + 41 + 151). If the total differs, note it.
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.
- 9d ago First seen · 43 lines · 57 tokens per session scan A d9bf1f0320cf
test-coverage is a skill published in the GitHub repository hoangsonww/WealthWise-Finance-Tracker (24 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 417 once invoked, about $0.0003 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
verify
Run this after every code change in this Node project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "audit". Diff audit (architecture, security, naming, error handling) → lint → tests + coverage gate. Coverage drops → add tests, never lower thresholds.…
prowler-test-sdk
Testing patterns for Prowler SDK (Python). Trigger: When writing tests for the Prowler SDK (checks/services/providers), including provider-specific mocking rules (moto for AWS only).
playwright
Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow). For Prowler-specific UI conventions under ui/tests, also use prowler-test-ui.
prowler-test-ui
E2E testing patterns for Prowler UI (Playwright). Trigger: When writing Playwright E2E tests under ui/tests in the Prowler UI (Prowler-specific base page/helpers, tags, flows).
tdd
Test-Driven Development workflow for ALL Prowler components (UI, SDK, API). Trigger: ALWAYS when implementing features, fixing bugs, or refactoring - regardless of component. This is a MANDATORY workflow, not optional.
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).