Borrowing it
Nothing to install: this file belongs to ethanrickyjrjr-wq/SWFL-Data-Gulf. 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/ethanrickyjrjr-wq/SWFL-Data-Gulf/main/.claude/skills/checks-burndown/SKILL.mdgit clone --depth 1 https://github.com/ethanrickyjrjr-wq/SWFL-Data-GulfWrote 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/ethanrickyjrjr-wq/swfl-data-gulf/checks-burndown)<a href="https://agentmods.dev/skills/ethanrickyjrjr-wq/swfl-data-gulf/checks-burndown"><img src="https://agentmods.dev/badge/skills/ethanrickyjrjr-wq/swfl-data-gulf/checks-burndown/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/ethanrickyjrjr-wq/swfl-data-gulf/checks-burndown"><img src="https://agentmods.dev/badge/skills/ethanrickyjrjr-wq/swfl-data-gulf/checks-burndown.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.00080 | $0.01748 |
| Opus 5.5 | $0.00032 | $0.00699 |
| Sonnet 5.5 | $0.00016 | $0.00350 |
| Haiku 4.5 | $0.00008 | $0.00175 |
Grade A, and why
checks-burndown 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 16d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 16d ago First seen · 124 lines · 80 tokens per session scan A 48a7d3809049
checks-burndown is a skill published in the GitHub repository ethanrickyjrjr-wq/SWFL-Data-Gulf (2 stars, last pushed yesterday), with no licence file. It adds 80 tokens to every session and 1,748 once invoked, about $0.0003 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-10-02.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.