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/create-issue/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/create-issue)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/create-issue"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/create-issue/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/create-issue"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/create-issue.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.00087 | $0.01469 |
| Opus 5 | $0.00044 | $0.00734 |
| Sonnet 5 | $0.00017 | $0.00294 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
create-issue 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue
Turns chat-surfaced problems/bugs (or user-provided text) into Todoist tasks in the Huntable CTI Studio project. Default section: Intake. User may override with a section name (e.g. "Up Next", "WIP").
When to use
- User says "Create Issue" or "create issue"
- User asks to log bugs/tasks from the conversation in Huntable CTI Studio/Todoist
Workflow
1. Gather content
- If user did not provide title/description: Summarize problems or bugs from the open chat into a single, clear issue (or one per distinct problem if that’s what the user wants).
- If user provided title and/or description: Use those; fill in only what’s missing from the chat.
2. Propose draft
Verbosity principle: Write the Description (and subtask descriptions) as if the implementing agent has never seen this conversation. Include: what is broken or needed, where in the codebase it lives (file paths, function names, relevant config keys if known), reproduction steps or triggering conditions, any constraints or prior decisions from the chat, and the expected outcome. A future agent should be able to implement correctly from the description alone — do not sacrifice completeness for brevity.
Output a single Create Issue Proposal in this shape:
## Create Issue Proposal
**Title:** [Short, actionable title]
**Description:**
[Full context for a cold agent: what’s wrong or needed, where it lives (files/functions/config),
how to reproduce or trigger it, any relevant constraints or decisions from the chat,
and what "done" looks like. Length should match complexity — do not truncate.]
**Section:** Intake *(or user-specified: Up Next | WIP | Someday / Maybe)*
**Subtasks:** *(none | or list below)*
- **1.** [Subtask title] — [What to do, where, and any non-obvious details]
- **2.** …
- Subtasks: Add them only when the issue naturally breaks into 2+ concrete, separate steps or sub-bugs. Otherwise use "(none)". Each subtask description should also be self-contained.
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 · 106 lines · 87 tokens per session scan A eecddfc90317
create-issue is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 1,469 once invoked, about $0.0004 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
building-identity-governance-lifecycle-process
Builds comprehensive identity governance and lifecycle management processes including joiner-mover-leaver automation, role mining, access request workflows, periodic recertification, and orphaned account remediation using IGA platforms. Activates for requests involving identity lifecycle management, JML processes…
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…
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
findings-tracker
../../../governance/findings-tracker/SKILL.md.
incident-commander
../../../response/incident-commander/SKILL.md.
os-workflow
A workflow guide for sending work from an AI Team OS project back into its task records. It explains how a lead agent and workflow agents record progress and important results.