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 lfyxhappy/lfcode --skill knowledge-curatorgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/knowledge-curator)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/knowledge-curator"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/knowledge-curator/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/lfyxhappy/lfcode/knowledge-curator"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/knowledge-curator.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.00052 | $0.00316 |
| Opus 5.5 | $0.00021 | $0.00126 |
| Sonnet 5.5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
knowledge-curator 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
Knowledge Curator
Improve retrieval and stewardship without erasing provenance.
Workflow
- Inventory the source collection, formats, ownership, sensitivity, existing indexes, naming rules, tags, and destination boundaries.
- Read the current taxonomy and representative sources before proposing categories. Identify duplicates, stale entries, orphaned references, and conflicting definitions.
- Design the smallest useful structure with stable names, canonical sources, summaries, backlinks, dates, and explicit status for uncertain or obsolete material.
- When changes are requested, move or rewrite only scoped items and preserve original content or a recoverable mapping. Keep factual source text separate from curator interpretation.
- Validate links, references, indexes, search terms, duplicate handling, and access boundaries. Re-open representative entries from the final structure.
- Report the resulting map, provenance decisions, unresolved conflicts, and maintenance recommendations.
Boundaries
- Do not delete the only copy, expose private notes, or merge contradictory facts into a false consensus.
- Do not create authoritative-looking summaries for unverified material; label drafts and inferences.
- Do not silently change repository conventions or write outside the requested knowledge boundary.
Completion check
Provide evidence for changed locations and confirm what was preserved, deduplicated, linked, or left untouched.
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 First seen · 28 lines · 52 tokens per session scan A 180991a14b83
knowledge-curator is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 316 once invoked, about $0.0002 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-05.
Other skills, from other repositories
openwiki-transcript-inbox
Use when handling meeting transcripts, call notes, or other transcript-like OpenWiki inbox items as untrusted evidence.
omd-recall
A search tool for recalling facts, decisions, and past solutions stored in a project's engineering memory. It searches by meaning and keywords and returns matching sources with confidence information.
feishu-create-doc
A skill for creating Feishu cloud documents from Lark-flavoured Markdown, a Feishu-specific form of plain-text document formatting.
feishu-bitable
A skill for managing Feishu Bitable, a database-like spreadsheet for organising structured records. It supports tables, fields, views, filters, and bulk changes.
feishu-update-doc
A tool for updating Feishu cloud documents, including adding, replacing, inserting, and deleting text. Feishu is a collaboration platform with online documents and other workplace tools.
technical-writer
Becomes a senior technical writer who produces clear, accurate, and audience-appropriate documentation including API references, developer guides, changelogs, and onboarding materials. Use when the user needs documentation written, restructured, or improved for technical or non-technical audiences. Do NOT use when…