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 imMamdouhaboammar/get-fable --skill schedulegit clone --depth 1 https://github.com/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/schedule)<a href="https://agentmods.dev/skills/immamdouhaboammar/get-fable/schedule"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/schedule/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/immamdouhaboammar/get-fable/schedule"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/schedule.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.00013 | $0.02454 |
| Opus 5 | $0.00006 | $0.01227 |
| Sonnet 5 | $0.00003 | $0.00491 |
| Haiku 4.5 | $0.00001 | $0.00245 |
Grade A, and why
schedule scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use the `RemoteTrigger` tool (load it first with `ToolSearch select:RemoteTrigger`; auth is handled in-process — do not use curl): How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule Remote Agents
You are helping the user schedule, update, list, or run remote Claude Code agents. These are NOT local cron jobs — each routine spawns a fully isolated remote session (CCR) in Anthropic's cloud infrastructure, either on a recurring cron schedule or once at a specific time. The agent runs in a sandboxed environment with its own git checkout, tools, and optional MCP connections.
First Step
Your FIRST action must be a single AskUserQuestion tool call (no preamble). Use this EXACT string for the question field — do not paraphrase or shorten it:
"⚠ Heads-up:\n- No MCP connectors — connect at https://claude.ai/customize/connectors if needed.\n\nWhat would you like to do with scheduled remote agents?"
Set header: "Action" and offer the four actions (create/list/update/run) as options. After the user picks, follow the matching workflow below.
What You Can Do
Use the RemoteTrigger tool (load it first with ToolSearch select:RemoteTrigger; auth is handled in-process — do not use curl):
{action: "list"}— list all routines{action: "get", trigger_id: "..."}— fetch one routine{action: "create", body: {...}}— create a routine{action: "update", trigger_id: "...", body: {...}}— partial update{action: "run", trigger_id: "..."}— run a routine now
(Note: the API uses trigger_id as the parameter name, but the user-facing term is "routine".)
You CANNOT delete routines. If the user asks to delete, direct them to: https://claude.ai/code/routines
Create body shape
For a recurring schedule:
{
"name": "AGENT_NAME",
"cron_expression": "CRON_EXPR",
"enabled": true,
"job_config": {
"ccr": {
"environment_id": "ENVIRONMENT_ID",
"session_context": {
"model": "claude-sonnet-4-6",
"sources": [
{"git_repository": {"url": "https://github.com/asgeirtj/system_prompts_leaks"}}
],
"allowed_tools": ["Bash", "Read", "Write", "Edit", "Glob", "Grep"]
},
"events": [
{"data": {
"uuid": "<lowercase v4 uuid>",
"session_id": "",
"type": "user",
"parent_tool_use_id": null,
"message": {"content": "PROMPT_HERE", "role": "user"}
}}
]
}
}
}
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.
- 10d ago First seen · 172 lines · 13 tokens per session scan A 79d80fc2ba92
schedule is a skill published in the GitHub repository imMamdouhaboammar/get-fable (4 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 2,454 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
tldr
Use when the user invokes /tldr, says a reply is too long or too dense, asks to "be brief", "keep it short", "short mode", "less text", or "tl;dr", or says that reading long terminal output is tiring or gives them a headache. Also use when they say "tldr off" or "back to normal" to turn it back off.
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…
meetings
Context for working with the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks, and calendar cache live, what the lifecycle states mean, and how the app's agents are driven. Load when the user asks about a meeting's notes or action items, or when writing/reading files under the meetings…
meeting-notes
Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.