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/lgtest/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/lgtest)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/lgtest"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/lgtest/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/lgtest"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/lgtest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 3 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00066 | $0.00920 |
| Opus 5 | $0.00033 | $0.00460 |
| Sonnet 5 | $0.00013 | $0.00184 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
lgtest 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LGTest — Review Changes & Propose Tests
Trigger: User says "LGTest" (or equivalent). Agent reviews recent changes and proposes new tests.
Workflow
1. Gather recent changes
Use (in order of relevance):
- Primary: Files modified or discussed in the current chat (edits, diffs, mentions).
- Secondary:
git statusandgit diff(uncommitted or last commit). - Optional: Recent commits or branch diff if user implied “branch” or “PR”.
Treat chat-edited paths as highest priority; git state as fallback or extension.
2. Map changes to test surface
For each changed or affected area, decide:
| Change type | Prefer | Location pattern |
|---|---|---|
| Routes, handlers, API | api | tests/api/test_*.py |
| Web UI, templates, JS | ui | tests/ui/test_*.py |
| Services, business logic | unit | tests/services/, tests/utils/, root tests/test_*.py |
| DB, queues, external deps | integration | tests/integration/test_*.py |
| Full user flows | e2e | tests/e2e/test_*.py |
| Startup, connectivity | smoke | tests/smoke/ |
Project rule: all test entry is via run_tests.py (smoke | unit | api | integration | ui | e2e).
3. Propose new tests
Output a LGTest Proposal in this shape:
## LGTest Proposal
### Changes in scope
- [path or area 1]
- [path or area 2]
### Proposed tests
| Type | Target / new file | Rationale |
|------|-------------------|-----------|
| unit | tests/services/test_foo.py | Covers new FooService.bar() |
| api | tests/api/test_baz_api.py | New /baz route |
| ui | tests/ui/test_baz_ui.py | New Baz page and buttons |
- Type: one of
unit,ui,smoke,api,integration,e2e. - Target: existing file to extend, or
tests/<category>/test_<name>.pyfor new. - Rationale: one line linking change to test (e.g. “New endpoint X”, “New workflow step Y”).
Add a short Implementation notes list only when useful (e.g. “reuse fixtures from test_bar_api.py”, “mark as @pytest.mark.ui”).
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.
- 11d ago First seen · 87 lines · 66 tokens per session scan A 6c76bc00d5ca
lgtest is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 920 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
test-generation
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.