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/djscheuf/agentic-dev-ecosystem-template/update-wikinpx skills add djscheuf/agentic-dev-ecosystem-template --skill update-wikigit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/update-wiki)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/update-wiki"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/update-wiki.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.00057 | $0.00761 |
| Opus 5 | $0.00028 | $0.00380 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
update-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 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.
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.
Wiki Update
After a session, update the project's vault/ so future sessions have the context.
When to Run
The session did at least one of:
- Made an architectural decision →
vault/decisions/ADR-NNN.md - Learned who owns a system →
vault/people/<name>.md+ link fromvault/services/<svc>.md - Fixed an incident →
vault/incidents/YYYY-MM-DD-<short>.mdwith root cause + fix + invariant to add toAGENTS.md - Added a term of art →
vault/glossary.md - Chose a library / service / pattern → capture the choice + the alternatives considered
If none of those happened, output "no wiki updates needed" and stop.
Process
- Read
vault/INDEX.mdto know the current shape of the wiki. - For each new fact, prefer updating an existing page. Only create new pages for genuinely new topics.
- Use
[[wikilinks]]between entities. If you reference a page that doesn't exist, create a stub with a "TODO" note. - Append-only. Never rewrite existing content. Mark stale sections with
> **Stale as of YYYY-MM-DD:** ...and add the new section below. - Update
vault/INDEX.mdwith any new pages. - Number ADRs sequentially — check the existing count in
vault/decisions/before picking a number. - Output a one-line summary of what you updated.
ADR Template
# ADR-NNN: <Decision title>
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-XXX
**Date:** YYYY-MM-DD
**Author:** <name or @role>
## Context
Why are we deciding this now? What forces are at play?
## Decision
What are we doing?
## Consequences
### Positive
-
### Negative
-
### Neutral / Follow-up
-
## Alternatives Considered
- **<Alternative 1>** — rejected because...
- **<Alternative 2>** — rejected because...
Incident Template
# YYYY-MM-DD: <One-line title>
**Severity:** SEV1 | SEV2 | SEV3
**Duration:** X hours
**Customer impact:** <facts, numbers>
## Timeline
- HH:MM — first symptom observed
- HH:MM — on-call paged
- HH:MM — mitigation started
- HH:MM — resolved
## Root cause
One paragraph. Factual, not blame-assigning.
## Contributing factors
- Factor 1
- Factor 2
## What went well
-
## What could have gone better
-
## Action items
- [ ] **<Owner>** — <action> — by <date>
## Invariant to add to AGENTS.md
(If this incident reveals a rule that should be constitutional, write it here and add to AGENTS.md.)
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 · 103 lines · 57 tokens per session scan A 9392663b0feb
update-wiki is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 761 once invoked, about $0.0003 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…