Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/rules/dfirtnt/huntable-cti-studio/agent-config-test-confirmation)<a href="https://agentmods.dev/rules/dfirtnt/huntable-cti-studio/agent-config-test-confirmation"><img src="https://agentmods.dev/badge/rules/dfirtnt/huntable-cti-studio/agent-config-test-confirmation/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/rules/dfirtnt/huntable-cti-studio/agent-config-test-confirmation"><img src="https://agentmods.dev/badge/rules/dfirtnt/huntable-cti-studio/agent-config-test-confirmation.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.00271 | $0.00271 |
| Opus 5 | $0.00135 | $0.00135 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
agent-config-test-confirmation 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 10d 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
Agent Config — Test Mutation Confirmation
Rule
You MUST double-check and get explicit confirmation from the user before:
- Creating new tests that mutate active agent configs (e.g., workflow config, agent prompts, LLM provider settings).
- Running existing tests that mutate active agent configs.
What Counts as Mutating Agent Configs
- Writing to or modifying workflow configuration files
- Changing agent prompts, presets, or prompt versions
- Altering LLM provider/model settings used by the running system
- Tests that call APIs or services that persist config changes to the active environment
Required Behavior
- Before proposing or implementing such tests: state that they will mutate agent configs and ask for explicit approval.
- Before running such tests: confirm with the user that they approve the run.
- Do not assume approval from "go", "implement", or "run tests" unless the user has explicitly confirmed they approve config-mutating tests.
Example
⚠️ These tests will modify active workflow/agent config. Do you approve running them?
Wait for explicit "yes" or equivalent before proceeding.
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.
- 10d ago First seen · 36 lines · 271 tokens per session scan A b428f2a95af7
agent-config-test-confirmation is a cursor rule published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 2d ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 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 cursor rules, from other repositories
frontend-preview
An offline preview and screenshot-checking workflow for the desktop interface. It replays saved AI event scenarios in the real interface, so developers can inspect intermediate streaming states without a backend or live AI service.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
detection-validation
The tests: section MUST have valid URLs, NOT placeholder descriptions.
linux-testing-workflow
Linux detection testing workflow and lessons learned.
workflow-architect
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.
testing-and-security
Testing and Security Guidelines for FastAPI Applications Including Unit Testing, Environment Variable Management, and Authentication Security.