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 agentmods add skills/tayontech/scope/scope-investigation-reportnpx skills add tayontech/SCOPE --skill scope-investigation-reportgit clone --depth 1 https://github.com/tayontech/SCOPEWrote 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/tayontech/scope/scope-investigation-report)<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="Measured on agentmods" 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 | $0.00036 | $0.00520 |
| Opus 5 | $0.00018 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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 5d 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 — 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, orINTELactive_hypothesisinvestigation_contextinvestigation_findingsKNOWLEDGE_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_CONTEXTentries 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:
- ...
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.
- 5d ago First seen · 97 lines · 36 tokens per session scan A 9de7c963cd16
scope-investigation-report is a skill published in the GitHub repository tayontech/SCOPE (54 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 520 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…