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/yarlson/yarstack/wiki-initializenpx skills add yarlson/yarstack --skill wiki-initializegit clone --depth 1 https://github.com/yarlson/yarstackWhat 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.00049 | $0.00346 |
| Opus 5 | $0.00024 | $0.00173 |
| Sonnet 5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
wiki-initialize 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.
What it actually says
Initialize a Yarbrain Wiki
Create the canonical vault only at a location the user approves. Never initialize or reconfigure a vault as an implicit side effect of installing the plugin.
Workflow
-
Confirm the vault path, whether it is personal or shared, and whether an existing directory must be adopted without overwriting content.
-
Confirm authority to write the Yarbrain config. Its default location is ~/.config/yarbrain/config.json; YARBRAIN_CONFIG can select another file.
-
Resolve ../../scripts/yarbrain.py relative to this SKILL.md and run:
python3 <helper> init <vault-path>Use --config only for an explicitly selected config path. Use --no-write-config when the user wants a vault without automatic hooks.
-
Verify that the command preserved existing files and created INDEX.md plus episodes/, notes/, skills/, inbox/, archive/, reports/, and .cache/.
-
Run the helper's lint command against the configured vault.
-
Report the vault and config paths, whether hooks can now find the vault, and any existing content that still needs adoption work.
The vault owns canonical Markdown. The config only locates it. Search indexes, session queues, and plugin installation directories are not canonical knowledge.
Do not import transcripts, create semantic notes, enable network access, or replace an existing index during initialization.
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 · 35 lines · 49 tokens per session scan A 5b1cae35b8ad
wiki-initialize is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 346 once invoked, about $0.0002 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
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
release-cli
Release a new version of the tokenmaxxing CLI to npm. Use when explicitly asked to release or publish @851-labs/tokenmaxxing, including checking main, bumping apps/cli/package.json, updating CHANGELOG.md, committing, tagging cli-vX.Y.Z, pushing, monitoring generated native package publishing, and smoke testing the…
ship-mobile-app
Build, change, debug, and prepare production mobile apps across domain meaning, local and server state, lifecycle, platform, and release boundaries. Use for non-trivial Flutter, React Native, iOS, or Android work involving persistence, sync, auth, offline behavior, notifications, permissions, native integrations…
verify-regression-tests
Verify that a regression test actually detects the defect it claims to guard against. Use after adding or reviewing a bug-fix guard, reproducing the original failure after a fix, or investigating a suspiciously green regression test. Do not use for general TDD, broad test-suite audits, mutation-score optimization…
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
repository-hygiene
Perform a read-only evidence-based audit of stale docs, agent files, scripts, generated artifacts, duplicate code, and optional tools. Use only when explicitly asked for cleanup or governance review; do not delete or refactor during the audit.