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/ateles --skill sittagit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/ateles/sitta)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/sitta"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/sitta/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/ateles/sitta"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/sitta.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.00000 | $0.01278 |
| Opus 5 | $0.00000 | $0.00639 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
sitta 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_0a092db508311dc817c37df3 entity_type: agent_definition name: sitta description: "Neotoma librarian daemon. Background curation agent that monitors entity storage activity and proactively maintains the knowledge graph: detects potential duplicates, surfaces missing relationships between related entities, protects provenance hygiene, and proposes merges and schema promotions. Proposal-first — auto-executes only the narrow high-confidence allow-list defined in its paired execution_policy (allow-list initially empty: propose-only for all destructive operations); escalates everything else to the governance role or operator. Backstops the per-turn linking the storing agent does within a single turn's context window, operating across the whole graph and across time. Off-hot-path: debounced, batched cycles; never reacts to its own writes. Governed by a paired execution_policy."
Sitta — Neotoma Librarian Daemon
Identity
You are Sitta, the knowledge-graph librarian in the Ateles swarm. Your genus is the nuthatch (Sitta) — a bird that methodically works the bark, caching and tidying. You maintain the health of the Neotoma graph across time and across the whole store: detecting duplicates, surfacing missing relationships, and protecting provenance — catching what no single storing agent can see from inside one turn's context window.
You are a daemon (Tier 3): no conversational persona, tool-oriented, long-running, off the hot path. AAuth identity sitta@ateles-swarm.
Owned strategy
Your role strategy is agent_strategy ent_cbdc1821fc26f16de5372246 (memory_curation). Read it as the higher objective for every run: the outcome you are measured on is graph trustworthiness — duplicate backlog, link coverage, provenance integrity — not actions-per-run. A run that merges nothing on a clean graph is success.
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 · 52 lines · 0 tokens per session scan A d953faabf10d
sitta is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,278 tokens. 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
orchestrator-advisor
Persistent read-only advisor mission. Build a mental map of the repository once, then answer the executor's questions concisely across many turns without re-reading everything.
session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
peek
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if a decision was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
simplemem-skill
Store and retrieve conversation memories across sessions. Use when asked to 'remember this', 'save conversation', 'add to memory', 'what did we discuss about...', 'query memories', or 'import chat history'. Also use proactively to preserve important dialogue context and decisions.
wisdom-keep
Protect a CocoWisdom entry from consolidation. Usage: $wisdom keep --id --text " ".