scope-detection-format

scope-detection-format is a skill for Claude Code, Codex from tayontech/SCOPE. It costs 33 tokens per session (1,208 once invoked), scanned A, original, MIT.

A formatting tool for turning already-made security detection decisions into standard Markdown, JSON, and dashboard records. A detection is a rule that looks for suspicious activity in logs or other data.

In plain words
What is it for?
Use it to create detections.md, detections.json, dashboard-ready Splunk sections, and control-schema records from a prepared detection list.
Why use it?
It keeps detection records consistent and machine-readable without changing the caller's detection logic or deciding whether a rule should be used. If required information is missing, it reports what prevents formatting.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create detections.md, detections.json, dashboard-ready Splunk sections, and control-schema records from a prepared detection list.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tayontech/scope/scope-detection-format
Install

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.

Any agent
npx skills add tayontech/SCOPE --skill scope-detection-format
Clone the repo
git clone --depth 1 https://github.com/tayontech/SCOPE

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for scope-detection-format

README.md
[![agentmods](https://agentmods.dev/badge/skills/tayontech/scope/scope-detection-format/github.svg)](https://agentmods.dev/skills/tayontech/scope/scope-detection-format)
Your own site
<a href="https://agentmods.dev/skills/tayontech/scope/scope-detection-format"><img src="https://agentmods.dev/badge/skills/tayontech/scope/scope-detection-format/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.

agentmods 80×15 button for scope-detection-format

Your own site · 80×15
<a href="https://agentmods.dev/skills/tayontech/scope/scope-detection-format"><img src="https://agentmods.dev/badge/skills/tayontech/scope/scope-detection-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01208
Opus 5.5 $0.00013 $0.00483
Sonnet 5.5 $0.00007 $0.00242
Haiku 4.5 $0.00003 $0.00121

Measured 2mo ago against content hash f3c8fbbf2459, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scope-detection-format 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 2mo 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.

skills/scope-detection-format/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scope Detection Format

This skill is format-only. It turns caller-provided detection decisions into the two controls artifacts: detections.md for humans and detections.json for the orchestrator, validator, and dashboard.

Boundary

The caller owns detection quality.

  • Do not decide alert vs hunt.
  • Do not promote, reject, or downgrade detections.
  • Do not change SPL logic.
  • Do not invent required values.
  • Do not add attack paths, event names, MITRE IDs, exclusions, noise controls, validation status, volume, or fidelity rationale that the caller did not provide.
  • If a required field is missing, return FORMAT_BLOCKS with the missing fields and affected detection names.

Inputs

Accept a caller-prepared detection list. Each detection must include these required fields:

  • name
  • type
  • objective
  • spl
  • severity
  • category
  • mitre_technique
  • source_attack_paths
  • source_public_exposure_findings
  • source_run_ids
  • promotion_decision
  • fidelity_rationale
  • noise_controls
  • expected_volume
  • validation_status

Optional fields:

  • covered_hops
  • coverage_caveats
  • tuning_guidance

Normalization

Only apply mechanical formatting:

  • Keep severity lowercase: critical, high, medium, low.
  • Keep type as atomic, composite, hunt_query, or coverage_gap.
  • Keep promotion_decision as alert, hunt_query, coverage_gap, or reject.
  • Keep expected_volume as low, medium, high, or unknown.
  • Keep validation_status as not_validated, validated, too_noisy, or failed.
  • SPL in detections.json must be a single-line string with literal newlines replaced by spaces.
  • Markdown SPL blocks must use fenced spl code blocks.
  • Dashboard-readable text must be concise and avoid long inline SPL in prose.

If a value cannot be normalized mechanically, return FORMAT_BLOCKS.

detections.md

Write sections in this order:

# SPL Detections

Generated from: {AUDIT_RUN_DIR}
Account: {ACCOUNT_ID}
Attack paths analyzed: {N}
Detections generated: {N}

---

## Attack Path: {attack_path_name}

**Severity:** {severity}
**Category:** {category}
**Validation Status:** {validated|conditional}
**Runtime Assumptions:** {runtime_assumptions[] or "none"}
**Coverage Caveats:** {coverage_caveats[] or "none"}
**MITRE:** {technique_ids}

### Detection: {detection_name}

- **MITRE:** {mitre_technique}
- **Severity:** {severity}
- **Type:** {atomic|composite|hunt_query|coverage_gap}
- **Promotion:** {alert|hunt_query|coverage_gap|reject}
- **Expected Volume:** {low|medium|high|unknown}
- **Fidelity Rationale:** {fidelity_rationale}
- **Noise Controls:** {noise_controls[]}
- **Related Attack Paths:** {source_attack_paths[]}
- **Description:** {objective}

```spl
{spl as readable multiline query}

False Positives: {false_positive_guidance if caller provided it, otherwise "Not provided."} Tuning Guidance: {tuning_guidance if caller provided it, otherwise "Not provided."}


Read the full file on GitHub · 156 lines

Changes

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.

  1. 2mo ago First seen · 156 lines · 33 tokens per session scan A f3c8fbbf2459

Subscribe to this mod's changes

scope-detection-format is a skill published in the GitHub repository tayontech/SCOPE (54 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,208 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens