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/thepm001/aep-agent-element-protocol/git-originnpx skills add thePM001/AEP-agent-element-protocol --skill git-origingit clone --depth 1 https://github.com/thePM001/AEP-agent-element-protocolWhat 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.00009 | $0.00026 |
| Opus 5 | $0.00005 | $0.00013 |
| Sonnet 5 | $0.00002 | $0.00005 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
git-origin 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 2d 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.
This is a copy
100% identical to git-origin — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
The source is not reproduced here
Licensed Apache-2.0
The repository is licensed Apache-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 6 lines · 9 tokens per session scan A a9dc8eb3eae9
git-origin is a skill published in the GitHub repository thePM001/AEP-agent-element-protocol (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 9 tokens to every session and 26 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-origin, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
tooloftruth
Use when verifying that a tool or skill was actually used, checking tool installation, or generating verification receipts. Triggers on 'verify', 'truth', 'proof', 'did it actually use', 'check tool', 'tooloftruth', '/truth'. Also triggers when the agent is about to claim a tool was used — run verification first.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
skill-vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…