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.
npx skills add dandye/ai-runbooks --skill close-case-artifactgit clone --depth 1 https://github.com/dandye/ai-runbooksWrote 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/dandye/ai-runbooks/close-case-artifact)<a href="https://agentmods.dev/skills/dandye/ai-runbooks/close-case-artifact"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/close-case-artifact/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/dandye/ai-runbooks/close-case-artifact"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/close-case-artifact.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.00045 | $0.00682 |
| Opus 5 | $0.00023 | $0.00341 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
close-case-artifact 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 12d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Case Artifact Skill
Close a case or alert with the required reason, root cause, and justification comment.
Inputs
ARTIFACT_ID- The ID of the case or alert to closeARTIFACT_TYPE- Either "Case" or "Alert"CLOSURE_REASON- Must be one of:MALICIOUS- Confirmed threatNOT_MALICIOUS- False positive or benignMAINTENANCE- System/maintenance activityINCONCLUSIVE- Unable to determineUNKNOWN- Unknown/other
ROOT_CAUSE- Must match a predefined root cause (useget_case_settings_root_causesto list options)CLOSURE_COMMENT- Detailed justification for closure- (Optional)
ALERT_GROUP_IDENTIFIERS- Alert group identifiers - (Optional, for alerts)
ASSIGN_TO_USER- User to assign closed alert to - (Optional, for alerts)
TAGS- Comma-separated tags
Workflow
Step 1: Execute Closure
For Cases:
secops-soar.siemplify_close_case(
case_id=ARTIFACT_ID,
reason=CLOSURE_REASON,
root_cause=ROOT_CAUSE,
comment=CLOSURE_COMMENT,
alert_group_identifiers=ALERT_GROUP_IDENTIFIERS
)
For Alerts:
secops-soar.siemplify_close_alert(
alert_id=ARTIFACT_ID,
reason=CLOSURE_REASON,
root_cause=ROOT_CAUSE,
comment=CLOSURE_COMMENT,
assign_to_user=ASSIGN_TO_USER,
tags=TAGS
)
Outputs
| Output | Description |
|---|---|
CLOSURE_STATUS |
Success/failure status of the closure |
Common Closure Patterns
| Scenario | Reason | Typical Root Cause |
|---|---|---|
| False Positive | NOT_MALICIOUS |
"Legit action", "Normal behavior" |
| Duplicate | NOT_MALICIOUS |
"Similar case is already under investigation" |
| Benign True Positive | NOT_MALICIOUS |
"Legit action" |
| Confirmed Threat (remediated) | MALICIOUS |
Varies by threat type |
| Unable to determine | INCONCLUSIVE |
"Insufficient data" |
Get Valid Root Causes
If unsure of valid root cause values:
secops-soar.get_case_settings_root_causes()
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.
- 12d ago First seen · 82 lines · 45 tokens per session scan A 81f89c09fae4
close-case-artifact is a skill published in the GitHub repository dandye/ai-runbooks (126 stars, last pushed 28d ago), licensed Apache-2.0. It adds 45 tokens to every session and 682 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…