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 steph-dove/klaussy-agents --skill rest-of-the-owlgit clone --depth 1 https://github.com/steph-dove/klaussy-agentsWrote 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/steph-dove/klaussy-agents/rest-of-the-owl)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/rest-of-the-owl"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/rest-of-the-owl/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/steph-dove/klaussy-agents/rest-of-the-owl"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/rest-of-the-owl.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.00090 | $0.02297 |
| Opus 5 | $0.00045 | $0.01149 |
| Sonnet 5 | $0.00018 | $0.00459 |
| Haiku 4.5 | $0.00009 | $0.00230 |
Grade A, and why
{{REPO}}-rest-of-the-owl 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 9d 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
86% identical to fastapi-rest-of-the-owl — 59 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
$ARGUMENTS
If $ARGUMENTS is empty, use the task definition the user pasted into the conversation (a ticket, a design note, a one-line ask). If there is none, stop and ask for one — this skill needs a target.
The bit
How to draw an owl: (1) draw two circles. (2) draw the rest of the owl. The user just handed you the two circles — a task definition. This skill draws the rest of the owl: the whole lifecycle from "here's what I want" to "here's a green, reviewed PR waiting for your merge." It is a genuine end-to-end run, not a gag — but it earns the name by doing the enormous unglamorous middle the meme skips over.
It does everything except merge. The merge button stays with the human. Never merge, never force-push over someone else's work, never mark the PR ready-to-merge on the user's behalf.
How this skill works
You orchestrate the repo's other skills as a pipeline. Each phase below names the sibling skill whose playbook you follow — open that skill's SKILL.md and run its steps, then come back here for the next phase. Track the whole run with TodoWrite: one todo per phase, in_progress when you start it, completed when it's done. The flow is long and mostly unattended; the todo list is how the user follows along.
Stop and hand back to the user (do not barrel ahead) if any phase hits something a human must decide: a missing secret or env var, an ambiguous requirement the task definition doesn't settle, a destructive migration, or a test failure that looks like a real bug in existing code rather than in your change.
Pre-flight — Permissions
If routine dev permissions are not yet configured for this worktree, invoke {{REPO}}-grant-permissions first so file editing, test execution, git operations, and forge CLI commands run unprompted throughout the loop.
Phase 1 — Plan
Follow {{REPO}}-plan (or {{REPO}}-implement's lighter planning phase for a small, single-surface task). Produce a concrete build sequence. Save the approved plan as an uncommitted OKF session note in $KLAUSSY_SESSION_NOTES_DIR/<agent-name>-plan.md (or %KLAUSSY_SESSION_NOTES_DIR%\<agent-name>-plan.md on Windows, or plan.md at worktree root) following the Open Knowledge Format protocol (YAML frontmatter with type: session-note, tags: [plan, design, devloop], generated: { by: <provider-id>/<agent-name>, at: <ISO-8601 timestamp> }). If the task definition leaves a real ambiguity, ask now — a wrong assumption here costs the whole owl.
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.
- 9d ago First seen · 102 lines · 0 tokens per session scan A 61e6eb7c1a38
{{REPO}}-rest-of-the-owl is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 15d ago), licensed MIT. It adds 90 tokens to every session and 2,297 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to fastapi-rest-of-the-owl, differing in 59 lines, and is treated as a copy.
Other skills, from other repositories
ensemble-beads-build
Drive an existing bead hierarchy to completion through the full builder, code-review, and close pipeline (Codex skill for /ensemble:beads-build).
jjj
Use when working in Jujutsu repositories for problem tracking, solution management, and code review — implements Popperian epistemology (problems → solutions → critiques) directly in version control.
github-guide
Use when managing GitHub tickets, Projects kanban, pull-request delivery/review, durable issue or PR context comments, or native CI/repository enforcement on github.com or GitHub Enterprise Server. Triggers on GitHub issues, issue relationships, gh issue, Projects v2 items/Status/fields, gh project, decision or…
goals
Drive a plan document to verified completion through a resumable single-writer backlog, named Worker Role research and review, worktree-isolated parallel builds, milestone gates, and a final adversarial teardown. Use when the user invokes /goal, asks to execute an architecture plan autonomously, resumes a goal, or…
issues
User-invoked. Sets up a project's tracker and CONTEXT/ once, then turns a grill into a spec and tracer-bullet tickets. Use when the user runs /issues.
review-health
Audit any repository's structural health and file the findings as proposed epics and one-PR issues.