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/lfyxhappy/lfcode/reportnpx skills add lfyxhappy/lfcode --skill reportgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWhat 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.00033 | $0.01672 |
| Opus 5 | $0.00016 | $0.00836 |
| Sonnet 5 | $0.00007 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
compose:report 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 yesterday.
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
91% identical to compose:report — 8 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Final Reports
Overview
Consolidate a feature's spec history into a single human-readable final report. The report presents the final implemented state as its primary content — what WAS BUILT, not what was tried. A brief Journey Log at the end captures notable failures and pivots for future designers.
Core principle: Final state first. The reader should understand the feature from this report alone, without reading any spec.
Announce at start: "I'm using the report skill to write the final report for this feature."
Save reports to: docs/compose/reports/<feature-name>.md
- No date in filename — the report is overwritten in place when the feature evolves
- Git history tracks revisions
- User preferences for report location override this default
Update Semantics
Specs are accumulative (new file per iteration). Final reports are overwrite (same file updated in place):
- If a report already exists for this feature, read it first, then overwrite with updated content
- Append new Journey Log entries from this iteration (don't discard previous entries)
- Update the
specsandplanslists to include any new entries
When to Use
Standard step after implementation is complete and verified — write a final report summarizing what was delivered.
Skip when:
- User explicitly asks to skip the report
- Change is trivially small (single bug fix, typo, config tweak) and not worth documenting
Checklist
- Identify all related specs and plans — find every iteration of this feature's design in specs/ and plans/
- Read the implemented code — understand what actually shipped (code is truth, not specs)
- Draft main sections — What Was Built, Architecture, Usage, Verification (scale each section to complexity: a few sentences if straightforward, detailed for complex features, but never longer than the plan)
- Draft Journey Log — brief flat bullet list, max 5 items
- Assemble report — combine sections, add frontmatter, save to reports/
- Self-review — verify report against code (not specs), check for placeholders, confirm length is proportional to feature complexity
- Mark specs and plans — prepend NOTE header to each spec and plan file
- Commit and transition — commit report + markers, invoke compose:merge
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.
- yesterday First seen · 181 lines · 33 tokens per session scan A cdbb32e78709
compose:report is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,672 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to compose:report, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
omd-video
视频→逐段结构化笔记 (MiMo-v2.5 原生吃画面+音频, 非 whisper 转写; 可重入管线)。讲解/课程视频里 PPT 框架图/代码/提示词是画面独有、音频拿不到的信息。产 ALL-NOTES.md 交 /omd-council 或 dagresearch 做综合。Trigger:/omd-video、抖音/B站/YouTube 讲解视频、课程系列、把这些视频学一遍/提炼、画面里有代码/图表/PPT。Skip:文字原文综合→/omd-council;网页内容→dagresearch(检索版)。.
omd-recall
主动召回 omd 自记忆:推理/写作/决策卡住时主动查既有事实,不等被动触发。经 memoryrecall 语义+词法混合检索,回带 confidence + source。Trigger:/omd-recall、查历史、以前怎么做的、翻一下记忆、有没有先例。.
convert-bullets
Generate Donahoe bullets across 4 types - Keyhole, Flip, Snapshot, Scar - mixed for rhythm. Each bullet is a miniature persuasion engine that creates a curiosity gap only the product resolves. Use when authoring the "what's inside" / "what you get" / feature section of a sales page, VSL, lead-magnet pitch, or course…
convert-lead-magnet-page
Author lead-magnet (free → email) opt-in pages: longer than a squeeze, full Method-compressed argument for why the freebie is worth the email. Emits brief + paste-ready HTML/CSS. Use when the user has a substantive free asset (guide, training, swipe file, audit, calculator) and needs a page that converts cold-to-cool…
convert-temperature
Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling. Sets length, depth, education burden, and approach for every other Method primitive that follows. Use when starting a new asset and you need to calibrate how much teaching, proof, and persuasion to load before writing. Not for…
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.