Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yideng966/LightAgentnpx agentmods add skills/yideng966/lightagent/knowledge-wikiWrote 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/yideng966/lightagent/knowledge-wiki)<a href="https://agentmods.dev/skills/yideng966/lightagent/knowledge-wiki"><img src="https://agentmods.dev/badge/skills/yideng966/lightagent/knowledge-wiki/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/yideng966/lightagent/knowledge-wiki"><img src="https://agentmods.dev/badge/skills/yideng966/lightagent/knowledge-wiki.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.00046 | $0.00933 |
| Opus 5.5 | $0.00018 | $0.00373 |
| Sonnet 5.5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
knowledge-wiki 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.
This is a copy
91% identical to knowledge-wiki — 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Wiki
Maintain a persistent, structured knowledge base in the knowledge/ directory.
Core Operations
1. Ingest — User shares an article, document, or resource
- Read and understand the source material
- Extract key facts, insights, and structured knowledge
- Determine the appropriate subdirectory:
- Read
knowledge/index.mdto see existing categories - If a matching category exists, follow that structure
- If not, create a new subdirectory with a clear name
- Read
- Create the knowledge page:
knowledge/<category>/<slug>.md - Update
knowledge/index.mdand append toknowledge/log.md
Source reliability for web materials:
- Prefer navigation links actually exposed on the page over guessed documentation paths.
- Only record URLs that were successfully fetched as Source in knowledge pages.
- 404/410, failed requests, or guessed paths must not be written as sources; if a page cannot be found, say so instead of saving unreliable content.
2. Synthesize — Conversation produces valuable structured knowledge
- Create a knowledge page under the appropriate category
- Update related pages with cross-references
- Update
knowledge/index.mdandknowledge/log.md
3. Query — User asks about accumulated knowledge
- Check
knowledge/index.md(already in your context) for relevant pages - Read specific pages with the
readtool - Supplement with
memory_searchif needed
Page Format
# Page Title
> Source: <URL or description of the original material>
Content here. Cross-reference related pages with markdown links:
[Related Page](../category/related-page.md)
## Key Points
- ...
## Related
- [Page A](../category/page-a.md) — how it relates
- [Page B](../category/page-b.md) — how it relates
The > Source: line records where the knowledge came from (URL, document name, conversation, etc.). Always include it when the material originates from a specific source.
For web sources, only use a URL here after it was successfully fetched or opened. Do not use guessed, failed, or 404/410 URLs as Source values.
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 · 103 lines · 46 tokens per session scan A 05cfbd02718e
knowledge-wiki is a skill published in the GitHub repository yideng966/LightAgent (22 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 933 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to knowledge-wiki, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.