Borrowing it
Nothing to install: this file belongs to dfirtnt/Huntable-CTI-Studio. 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/dfirtnt/Huntable-CTI-Studio/main/.cursor/skills/codebase-test-trueup/SKILL.mdgit clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/dfirtnt/huntable-cti-studio/codebase-test-trueup)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/codebase-test-trueup"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/codebase-test-trueup/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/dfirtnt/huntable-cti-studio/codebase-test-trueup"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/codebase-test-trueup.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.00096 | $0.05972 |
| Opus 5 | $0.00048 | $0.02986 |
| Sonnet 5 | $0.00019 | $0.01194 |
| Haiku 4.5 | $0.00010 | $0.00597 |
Grade A, and why
codebase-test-trueup 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.
How it starts
The opening of the file, as written. The whole thing — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Test True-Up
Systematically identify and close test coverage gaps. The goal is raising unit-level coverage on the code that matters most — recently changed, high-risk, or session-relevant modules — without generating low-value or redundant tests.
Philosophy
Coverage is a proxy for confidence. Chasing 100% is wasteful; ignoring gaps is reckless. This skill targets the intersection of low coverage and high change frequency — the code most likely to regress. Tests generated here must be stateless unit tests that run without Docker, databases, or network access.
Scope boundaries
In scope: Source files under src/ that can be meaningfully unit-tested with mocks. Test output lands in the appropriate tests/ subdirectory following existing conventions.
Off limits:
AGENTS.md,CLAUDE.md— never modify- Integration, API, UI, or E2E tests — those require containers and belong to dedicated workflows
- Refactoring source code to improve testability — tests adapt to the code, not the other way around
- Deleting or modifying existing tests — this skill only adds
Bugfix Detection & Regression Tests (applies to all modes)
Every mode in this skill must actively look for bugfixes and evaluate whether regression tests exist. A bugfix without a regression test is a bug that can come back.
How to detect bugfixes
Bugfixes surface through multiple signals. Check all of them:
1. Commit message prefixes (for audit and fill modes):
# Conventional-commit prefixes used in this repo:
git log --oneline -50 | grep -E '^\w{8} (fix|security|revert)(\(|:)'
The prefixes fix:, fix(scope):, security:, and revert: all indicate code that corrected broken behavior.
2. Session context (for scope mode): When working in a chat session, identify bugfixes from:
- The user describing a bug ("X is broken", "Y returns wrong value", "Z crashes when...")
- The user referencing an issue or error report
- Code changes that modify conditional logic, add null checks, fix off-by-ones, correct type handling, or add missing error handling
- Changes described with words like "fix", "patch", "correct", "handle", "prevent", "guard"
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 · 643 lines · 96 tokens per session scan A 833ef67e3816
codebase-test-trueup is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 5,972 once invoked, about $0.0005 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
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
configuring-windows-event-logging-for-detection
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving…
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
python-testing
Write or modify Python tests. Use when: adding new tests, understanding testing conventions, working with fixtures, writing FastAPI route tests, database tests, or following pytest patterns. DO NOT USE FOR RUNNING TESTS. If you are just running tests, not building them, you do not need this.
Write tests
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
unit-test
Testing patterns for the Python/FastAPI + React/TypeScript stack. Covers pytest configuration, conftest fixtures, database safety guards, external API mocking, async tests, Celery eager mode, and Vitest for frontend.