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/oleg494/coding-kit/dev-wikinpx skills add oleg494/coding-kit --skill dev-wikigit clone --depth 1 https://github.com/oleg494/coding-kitWhat 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.00120 | $0.00855 |
| Opus 5 | $0.00060 | $0.00428 |
| Sonnet 5 | $0.00024 | $0.00171 |
| Haiku 4.5 | $0.00012 | $0.00085 |
Grade A, and why
dev-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 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Wiki — cross-chat developer memory
Always-on skill. Knowledge base: decisions, bugs, patterns, architectural decisions.
Memory lives in ~/.memory/ (global + per-project hierarchy; env MEMORY_ROOT overrides).
Boundary rule
| Knowledge | Where | Index |
|---|---|---|
| Portable (patterns, lessons, decisions) | ~/.memory/Wiki/<type>/ |
python ~/.memory/db-tools/build.py |
| Project-specific (status, configs, context) | WORK/<project>/docs/ |
python ~/.memory/db-tools/build.py -r <root> -o ~/.memory/db/<name>.db |
Knowledge lives/dies with the project → project; portable across projects → global Wiki.
Save reflex (proactive, not only on request)
- On every finished task / made decision / closed bug — 10-second check: would a future session need this? Yes → save. No → skip (noise-free is deliberate).
- Conclusions →
findings.py add; portable patterns → Wiki; realizations by trigger below.
Record types (global Wiki)
| Type | Folder | When |
|---|---|---|
reference |
~/.memory/Wiki/reference/ |
Fact, documentation, knowledge |
howto |
~/.memory/Wiki/howto/ |
Instruction, guide |
error |
~/.memory/Wiki/errors/ |
Bug, incident, lesson learned |
decision |
~/.memory/Wiki/decisions/ |
ADR, architectural decision |
idea |
~/.memory/Wiki/ideas/ |
Idea |
Workflow — save (global)
- Determine the type → folder in
~/.memory/Wiki/. - Create file
~/.memory/Wiki/<type>/<slug>.mdwith frontmatter:--- type: reference title: "Title" description: "About what" date: 2026-08-15 tags: [category, topic] --- - Update
~/.memory/Wiki/index.md. - Append to
~/.memory/Wiki/log.md. python ~/.memory/db-tools/build.pypython ~/.memory/db-tools/lint_wiki.py- Important conclusion →
python ~/.memory/db-tools/findings.py add "topic" --text "conclusion" --source path
Workflow — search
python ~/.memory/db-tools/search_all.py "query" # all databases at once
python ~/.memory/db-tools/search_all.py "query" --substring # declensions/substrings
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 · 75 lines · 120 tokens per session scan A 46bf14f165e3
dev-wiki is a skill published in the GitHub repository oleg494/coding-kit (1 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 855 once invoked, about $0.0006 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-31.
Other skills, from other repositories
spec-kitty-orchestrator-api-operator
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external…
excalidraw
Generate an Excalidraw whiteboard in Sean's hand-drawn video style (Excalifont, roughness 1, green signature, socials + watermark, source labels). Use whenever the user wants a whiteboard, diagram, teaching board, or "chart" for a video or the docs/whiteboards gallery — anything Sean will film with.
weekly-brief
Brief me on my week, my day, or what to focus on. Use for "brief me", "what's on my week", "what should I focus on", "my day", "catch me up", morning briefing.
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
levelup-specify
Extract Context Directive Records (CDRs) from the current session after completing work. Identifies reusable patterns (rules, personas, examples, evals) and captures directive compliance cases for team-ai-directives.
logion
Compact bootstrap skill for recall-first Logion discovery, inspection, install, update, and creator-course-management routing without loading the whole marketplace.