agentmods.dev

scope-investigation-report

scope-investigation-report is a skill for Claude Code, Codex from tayontech/SCOPE. It costs 36 tokens per session (520 once invoked), scanned A, original, MIT.

A template for a facts-only report after a SCOPE security investigation. It includes a summary, evidence timeline, query appendix, known gaps, and optional saved investigation material; SCOPE is the surrounding security-analysis workflow.

In plain words
What is it for?
Use it to record investigation findings with UTC times, principals, source addresses, event details, queries, and relevant prior knowledge.
Why use it?
It keeps reports tied to returned evidence and clearly separates unknowns, skipped steps, and missing telemetry from conclusions.

Skill for Claude CodeCodex

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

not rated 54repo 4mo ago A scan 36 tokens original MIT

Good fit Use it to record investigation findings with UTC times, principals, source addresses, event details, queries, and relevant prior knowledge.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tayontech/scope/scope-investigation-report
View source ↗ tayontech/SCOPE
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-investigation-report
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-investigation-report

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tayontech/scope/scope-investigation-report"><img src="https://agentmods.dev/badge/skills/tayontech/scope/scope-investigation-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 520 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.00036 $0.00520
Opus 5.5 $0.00014 $0.00208
Sonnet 5.5 $0.00007 $0.00104
Haiku 4.5 $0.00004 $0.00052

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

Security

Grade A, and why

scope-investigation-report 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-investigation-report/SKILL.md · 97 lines

How it starts

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

SCOPE Investigation Report

Use this skill after the analyst chooses done in scope-investigate, before the save prompt and before durable knowledge updates.

The top-level investigation agent provides:

  • MODE: INVESTIGATION, RUN, or INTEL
  • active_hypothesis
  • investigation_context
  • investigation_findings
  • KNOWLEDGE_CONTEXT
  • skipped steps and analyst pivots
  • saved artifact path when persistence was approved

Rules

  • Present facts only. Do not assign severity, risk, suspicion, compromise, maliciousness, or confidence.
  • Do not infer events that no query returned.
  • Do not hide skipped steps or telemetry gaps.
  • Prefix every follow-up option with Consider:.
  • Cite KNOWLEDGE_CONTEXT entries only when they influenced reasoning.
  • Use UTC timestamps.
  • Deduplicate events that appeared in overlapping query windows.

Required Sections

Return this structure:

## Investigation Summary

[2-5 sentences. State what the data showed, what the data did not show, and what remains unknown.]

## Evidence Timeline

| Timestamp (UTC) | Event | Principal | Source IP | Details |
|-----------------|-------|-----------|-----------|---------|

## Key Indicators Found

- [Observable fact]

## Investigation Gaps

- [Skipped step, missing telemetry, or unanswered question]

## Environment Context Used

| Entity | Knowledge Entry | How It Informed Investigation |
|--------|-----------------|-------------------------------|

## Suggested Follow-Up Actions

- Consider: [optional next step]

Omit Environment Context Used when no knowledge entry influenced the investigation.

Saved Artifact Appendix

When the analyst approves save, append:

## Queries Run

| Step | Purpose | SPL | Result Summary |
|------|---------|-----|----------------|

## Skipped Or Pivoted Steps

| Step | Status | Reason |
|------|--------|--------|

Output Contract

Return:

INVESTIGATION_REPORT
  status: complete|skipped|error
  sections:
    - Investigation Summary
    - Evidence Timeline
    - Key Indicators Found
    - Investigation Gaps
    - Suggested Follow-Up Actions
  save_ready: true|false
  knowledge_update_candidates:
    - ...

Read the full file on GitHub · 97 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 · 97 lines · 36 tokens per session scan A 9de7c963cd16

Subscribe to this mod's changes

scope-investigation-report is a skill published in the GitHub repository tayontech/SCOPE (54 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 520 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.

ResearchSecurity
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