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/lynxlangya/knowject/knowject-memory-capturenpx skills add lynxlangya/knowject --skill knowject-memory-capturegit clone --depth 1 https://github.com/lynxlangya/knowjectWrote 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/lynxlangya/knowject/knowject-memory-capture)<a href="https://agentmods.dev/skills/lynxlangya/knowject/knowject-memory-capture"><img src="https://agentmods.dev/badge/skills/lynxlangya/knowject/knowject-memory-capture.svg" alt="Measured on agentmods" 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 | $0.00153 | $0.02078 |
| Opus 5 | $0.00077 | $0.01039 |
| Sonnet 5 | $0.00031 | $0.00416 |
| Haiku 4.5 | $0.00015 | $0.00208 |
Grade A, and why
knowject-memory-capture 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
8 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.
- agents/openai.yaml 911 B
- README.md 2.7 KB
- references/examples/memory-input-summary.md 1.0 KB
- references/examples/project-memory.expected.yaml 2.1 KB
- references/memory-file-contract.md 3.1 KB
- references/memory-taxonomy.md 2.6 KB
- references/source-selection.md 2.7 KB
- scripts/validate-project-memory.py 6.3 KB runs code
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.
- 3d ago First seen · 190 lines · 153 tokens per session scan A 5c70232a3558
knowject-memory-capture is a skill published in the GitHub repository lynxlangya/knowject (56 stars, last pushed 3mo ago), with no licence file. It adds 153 tokens to every session and 2,078 once invoked, about $0.0008 per session on Opus 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-08-30.
Other skills, from other repositories
gsd:new-project
Initialize a new project with deep context gathering and PROJECT.md. Creates project structure, requirements, roadmap, and state.
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator or diagnose-issues workflow.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by plan-phase orchestrator.
gsd-verifier
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed.
gsd-codebase-mapper
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area.