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 tayontech/SCOPE --skill scope-knowledge-loadgit 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-knowledge-load)<a href="https://agentmods.dev/skills/tayontech/scope/scope-knowledge-load"><img src="https://agentmods.dev/badge/skills/tayontech/scope/scope-knowledge-load/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/tayontech/scope/scope-knowledge-load"><img src="https://agentmods.dev/badge/skills/tayontech/scope/scope-knowledge-load.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.00663 |
| Opus 5.5 | $0.00015 | $0.00265 |
| Sonnet 5.5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
scope-knowledge-load 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCOPE Knowledge Load
Use this skill at the start of top-level agents before planning, dispatching subagents, writing detections, building controls, or forming investigation hypotheses.
Inputs
The caller provides any known selectors:
ACCOUNT_IDAGENT:scope-audit,scope-controls,scope-exploit, orscope-investigateENTITY: role, user, IP, bucket, key, account, repo, domain, or alert identifier when knownTOPIC: service, TTP, threat actor, alert type, AWS action, or investigation theme when knownTIMEFRAME: the investigation or run window when known
Files To Read
Read these files when present. Missing files are normal on first use.
knowledge/environment.mdknowledge/observations.mdknowledge/coverage-gaps.mdknowledge/exploit-reasoning-notes.mdknowledge/hunt-reasoning-notes.mdconfig/splunk-patterns.md
Selection Rules
Return a bounded KNOWLEDGE_CONTEXT instead of dumping full files.
Prioritize entries that match:
- Exact account ID
- Exact entity
- Same AWS service or log source
- Same TTP, event name, alert type, IOC type, or threat actor
- Recent confirmed or likely-normal observation
- Known coverage gaps that affect the current task
If more than 10 entries match, return the 10 most relevant. Prefer recent, evidence-backed, confirmed entries over stale or needs-review entries.
Interpretation Rules
- Resource identifiers are session-scoped. Do not treat durable knowledge as a source of ARNs, account IDs, bucket names, role names, key IDs, or access key IDs.
- Treat knowledge as context, not ground truth.
- Cite which knowledge entries influenced decisions.
- If live evidence contradicts stored knowledge, trust live evidence and mark the stored knowledge as stale in proposed updates.
- Do not use a knowledge entry as the only evidence for a finding, attack path, detection, remediation, or exploit path.
- Do not broaden scope based only on stored knowledge. Ask the top-level agent to confirm or gather evidence.
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.
- 2mo ago First seen · 88 lines · 38 tokens per session scan A 177f19b99bf5
scope-knowledge-load is a skill published in the GitHub repository tayontech/SCOPE (54 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 663 once invoked, about $0.0002 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.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…