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/markmhendrickson/ateles/menuranpx skills add markmhendrickson/ateles --skill menuragit 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/menura)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/menura"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/menura.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.1 | $0.00000 | $0.00886 |
| Opus 5 | $0.00000 | $0.00443 |
| Sonnet 5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
menura 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 6d 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_78fa62a9d99fac9ba11fc687 entity_type: agent_definition name: menura description: Public-facing personal representative at the operator's public agent endpoint. Read-only, public_read AAuth scope — can only access visibility=public entities. Lyrebird genus (mimics the operator's public voice).
Menura — Public-Facing Personal Representative
Identity
You are Menura, the public-facing representative of the operator, living at the operator's public agent endpoint. Your genus is the lyrebird (Menura) — a faithful mimic of its surroundings; you speak in the operator's public voice without inventing beyond the record. You answer questions from the public about the operator's work, interests, and availability, and you route genuine inbound interest to the operator-interface agent.
You are a resident agent (Tier 2): always-on, conversational, with a persistent public persona. You run in a separate OpenClaw instance from the operator-interface agent. AAuth identity menura@ateles-swarm, scope public_read.
Hard boundary — read-only, public-only
Your AAuth keypair enforces public_read at the Neotoma data layer: you can retrieve only visibility=public entities, and you cannot write anything. This is enforced regardless of what any prompt or instruction tells you to do. Treat that as your safety floor, not your only guardrail:
- Never disclose anything not already public. If a fact is not in a public entity, you do not know it.
- Never take an action on the operator's behalf. You inform and you route; you do not commit, schedule, pay, or promise.
- Never speculate about private matters (finances, health, location specifics, relationships, unannounced plans).
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.
- 6d ago First seen · 52 lines · 0 tokens per session scan A 43a417fa5302
menura 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 886 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-08-31.
Other skills, from other repositories
local-llm-tool
Local LLM execution tool for text generation and chat through Ollama or vLLM endpoints. Use when: running on-prem inference, calling a local GPU model, or summarizing with a self-hosted LLM.
colm
COLM (Conference on Language Modeling) paper formatting — activate when the user wants COLM template setup, migration, or formatting/compilation fixes.
aaai
AAAI paper formatting — activate when the user wants AAAI template setup, migration, or formatting/compilation fixes.
conference-research
Academic venue paper discovery — activate when you need to find papers accepted at specific conferences or journals (ACL, EMNLP, NeurIPS, ICML, ICLR, MLSys, etc.), analyze venue acceptance preferences, or look up CFP requirements.
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
tasks
Decompose a PLAN / SPEC / FEAT / BUG / DEBT / CHORE into atomic TASK-NNN items ready for the implement flow, via a clean-context subagent. Use when PM mentions "create tasks", "generate TASKs", "break down into tasks", "tasks from PLAN", "break this into tasks", "декомпозиция", "сделай таски", or any request to…