Borrowing it
Nothing to install: this file belongs to fifeqqs1/MortyClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fifeqqs1/MortyClaw/main/.agents/skills/mortyclaw-tools/SKILL.mdgit clone --depth 1 https://github.com/fifeqqs1/MortyClawWrote 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/fifeqqs1/mortyclaw/mortyclaw-tools)<a href="https://agentmods.dev/skills/fifeqqs1/mortyclaw/mortyclaw-tools"><img src="https://agentmods.dev/badge/skills/fifeqqs1/mortyclaw/mortyclaw-tools/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/fifeqqs1/mortyclaw/mortyclaw-tools"><img src="https://agentmods.dev/badge/skills/fifeqqs1/mortyclaw/mortyclaw-tools.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.00030 | $0.00542 |
| Opus 5.5 | $0.00012 | $0.00217 |
| Sonnet 5.5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
mortyclaw-tools 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 1mo 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.
What it actually says
MortyClaw tools
Use mcp__mortyclaw__feishu_* for Feishu documents and messages,
mcp__mortyclaw__zotero_* for the local read-only literature library, and
mcp__mortyclaw__arxiv_* for public-paper search and reading. Use
mcp__mortyclaw__memory_* only when the user refers to prior work, and
mcp__mortyclaw__task_* for scheduled work.
Use mcp__mortyclaw__research_retrieve only when an answer needs evidence from the user's
indexed papers or documents and the current context does not already contain enough
[RETRIEVED_EVIDENCE]. Do not retrieve for ordinary chat, code questions, rewriting,
translation, or summarizing text already supplied by the user. The presence of words such as
"paper" or "research" alone is not a reason to retrieve. Cite the returned evidence IDs. If an
existing retrieval lacks a new aspect, call with mode=expand and its prior_retrieval_id;
otherwise use the evidence already in context without another call.
For conceptual or topic-based discovery in the indexed Zotero library, prefer
mcp__mortyclaw__research_retrieve with sources=["zotero"]. Use direct Zotero search for exact
title, author, year, citation key, collection, or item-key lookup, or when the research index has
no matching evidence. Zotero's optional Chroma semantic-search tool is intentionally unavailable;
MortyClaw uses the shared Qdrant research index for semantic retrieval.
mcp__mortyclaw__research_index_document, research_remove_document, and
research_sync_zotero change the local knowledge index and therefore require approval.
Every MortyClaw MCP call must include the exact context_token supplied in the current trusted
runtime context. Pass it unchanged to delegated subagents. It locates the current turn and never
bypasses policy.
Writes, downloads, monitoring changes, task changes, shell commands, and file changes are staged
for MortyClaw approval. Do not retry an approval_required response and do not use another tool to
bypass approval. Explain the proposed operation and let MortyClaw present the approval batch.
Zotero is always read-only. Search and read before requesting any external modification.
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.
- 1mo ago Changed · +17 lines a66f715b0baf
- 1mo ago First seen · 23 lines · 30 tokens per session scan A 2e7103dc538c
mortyclaw-tools is a skill published in the GitHub repository fifeqqs1/MortyClaw (24 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 542 once invoked, about $0.0001 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-09-19.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.