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 markmhendrickson/neotoma --skill get-contextgit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/get-context)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/get-context"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/get-context/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/markmhendrickson/neotoma/get-context"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/get-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 31 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00067 | $0.00903 |
| Opus 5 | $0.00034 | $0.00451 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
get-context 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 7d 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.
get-context
Specification status: This file is a specification, not a runnable skill. The core_workflows bundle is defined in m1 of the Bundles Strategy (plan ent_089da2ecebc3bd804d63dcf2); the runtime path that installs and auto-loads these skills lands in m2 alongside plan ent_b5a51d1395d206e10945b6b1 (Resolve #205). Until m2, treat this file as the locked spec the implementation MUST match.
Adapted in structure from the reference implementation in lemon-skills-share (https://github.com/Lemonbrand/lemon-skills-share).
Purpose
Synthesize a context brief about a target entity before substantive work begins. The output is a synthesized brief, not a raw data dump. Depth scales with caller intent via the depth_tiers field.
When to use
- Before drafting any output (email, decision memo, deck, code change) that depends on prior state.
- Before any conversation where the user wants to walk in primed.
- When the user names a person, company, or project and asks "what do we know".
Required entity types
contact, event, task, observation, conversation, conversation_message. All provided by the default-install core bundle.
Depth tiers
| Tier | Scope | When to use |
|---|---|---|
snapshot |
Current entity snapshot only. No history, no graph walk. | Quick orientation; agent has most context already. |
standard |
Snapshot, recent observations (last 30 days), linked open tasks, last 5 communication touchpoints. | Default. Covers most pre-work briefs. |
full |
Standard plus full observation history, all linked tasks, all communication threads, one-hop graph walk. | Decision memos, due diligence, escalations. |
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.
- 7d ago First seen · 88 lines · 67 tokens per session scan A f905d849771e
get-context is a skill published in the GitHub repository markmhendrickson/neotoma (32 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 903 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
remember
Routes user requests containing "remember", "recall", "checkpoint", "session", "todo", or "where were we" to the correct OpenEmpiric (OEM) MCP tool. Use when the user wants to persist, retrieve, or contextualize knowledge from project memory.
akf
Trust metadata for files, memories, and skills — check before you trust, stamp what you verify. A stamp costs 15 tokens; re-verifying costs 15,000.
akf
Trust metadata for files, memories, and skills — check before you trust, stamp what you verify. Use before building on existing files, after completing verified work, and when handling agent memories or downloaded skills.
aoa-memo
AoA/Abyss durable memory and owner orientation: use when ongoing work may depend on reviewed prior decisions, provenance, lifecycle/currentness, or an existing memo artifact, even when none is named. Also use to recall, review, or evolve a candidate, export, quarantine packet, object, corpus identity, lifecycle…
soul-archive
Soul Archive — A digital personality persistence system + agentic memory. Builds your digital soul clone through everyday AI conversations, with proactive context injection, cross-session recall, failure-pattern warning, and pattern distillation. All data stored locally as plaintext JSON. Six modes: Soul Extract, Soul…
mk:wiki
Capture, gate, query, and render long-term project knowledge through the gated mewkit wiki subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates…