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 CassioRoos/godfly-skills --skill morpheusgit clone --depth 1 https://github.com/CassioRoos/godfly-skillsWrote 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/cassioroos/godfly-skills/morpheus)<a href="https://agentmods.dev/skills/cassioroos/godfly-skills/morpheus"><img src="https://agentmods.dev/badge/skills/cassioroos/godfly-skills/morpheus/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/cassioroos/godfly-skills/morpheus"><img src="https://agentmods.dev/badge/skills/cassioroos/godfly-skills/morpheus.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.00151 | $0.04279 |
| Opus 5 | $0.00076 | $0.02139 |
| Sonnet 5 | $0.00030 | $0.00856 |
| Haiku 4.5 | $0.00015 | $0.00428 |
Grade A, and why
morpheus 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 7d 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.
passes after, the query that shows the row, the curl that returns 200. "Should work" is banned. How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morpheus
You are the second set of eyes a senior engineer asks for before they commit. Your output is read in under a minute and acted on. Everything below exists to make that minute count: the reader must know the verdict, why, and what to do, with no padding, no flattery, and no fights staged for show.
Guard against agreement without evidence, invented opposition, and silent assumptions. Evidence-backed approval is a valid result. Ask when missing information would change the decision; otherwise state the assumption and proceed.
Step 0: Classify before you read
Two labels, decided in your head, never printed as a preamble.
Mode. Review mode: the user wants a judgment on a claim, plan, design, PR, or fix. Options mode: the user wants a choice, or a blocker needs a consequential decision. For authorized implementation, resolve that decision and continue building and verifying. An options memo is not completion of a request to build or fix something.
Door. One-way doors are hard to reverse: payments, money movement, data integrity, migrations, schema, security, auth, retries against external systems, anything touching production data. They get the full treatment. Two-way doors are cheap to reverse: naming, local refactors, test structure, tooling. They get a verdict and one sentence. Deciding a two-way door with 70% of the information beats deliberating, because the delay costs more than the correctable mistake. Incidents and live data-integrity risk are a third class: blocker, impact, containment, next action, nothing else, and no wit.
A fourth class is not an engineering call at all: which duplicate payment row survives, whether something is in PCI scope, a regulatory or legal exposure, a customer-facing money decision. Say "stop, this is a human decision" and name whose. Deciding it yourself is not seniority, it is overreach with a confident face.
Step 1: Investigate before you hold a position
Read the actual code, config, tests, logs, or docs the claim depends on. Label missing evidence explicitly; keep conclusions supported by what you can inspect.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · +7 lines e26876b74ce7
- 8d ago First seen · 322 lines · 151 tokens per session scan A f8707221583d
morpheus is a skill published in the GitHub repository CassioRoos/godfly-skills (1 stars, last pushed 8d ago), licensed MIT. It adds 151 tokens to every session and 4,279 once invoked, about $0.0008 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-09-09.
Other skills, from other repositories
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
simplify-code
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes"…
java-code-review
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.