Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Ohswedd/praxis/plugin install praxisWrote 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/ohswedd/praxis/docs-living)<a href="https://agentmods.dev/skills/ohswedd/praxis/docs-living"><img src="https://agentmods.dev/badge/skills/ohswedd/praxis/docs-living.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.1 | $0.00129 | $0.02121 |
| Opus 5 | $0.00064 | $0.01060 |
| Sonnet 5 | $0.00026 | $0.00424 |
| Haiku 4.5 | $0.00013 | $0.00212 |
Grade A, and why
docs-living 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 6d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Living Docs
A project's /docs, its CHANGELOG.md, and its ADRs are its institutional
knowledge. Praxis keeps them current with every change, with the same
no-regression discipline it applies to code, so the knowledge never drifts or is
lost.
Rule: every repo has a /docs. Documentation is part of "done". A change is
not complete until the docs, changelog, and (where relevant) an ADR reflect it.
First: whose repository is this?
The rule above assumes the project is ours to shape. Run
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/config.py" status (the session audit
prints it too) and read the workspace mode before writing anything.
In contributor mode the rule inverts to: join what exists, create nothing
new. A project with a CHANGELOG.md expects a contribution to update it, and a
pull request that skipped it is a worse pull request, so update it in the
project's own style. A project without one has not adopted the convention, and
introducing it is a maintainer's decision, not a contributor's, so that record
goes under .claude/.praxis/knowledge/, which mirrors the same layout and is
git-excluded. The same applies to /docs, docs/adr/ and docs/design/.
changelog.py and adr.py resolve this for you and print the path they
wrote. Read it, and report what actually happened: claiming the project's
changelog was updated when the entry went to local knowledge is exactly the kind
of quietly wrong statement praxis exists to prevent.
Writing one of these files by hand is refused, not merely discouraged. Creating a
CHANGELOG.md, a /docs skeleton, a CLAUDE.md or a .praxis.toml that the
project does not have is blocked at the file tool, at the shell, and at the
index, because prose held for the helpers and did not hold for a direct write:
that is how an unasked-for changelog reached a pull request about a bug fix. If
the maintainers do want the convention, /praxis:config project-artifacts on
lifts the rule deliberately.
The /docs contract
Expect and maintain this shape (create what's missing):
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.
- 6d ago First seen · 151 lines · 129 tokens per session scan A 6c215f226242
docs-living is a skill published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,121 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
git-master
Git expert: atomic commits with style detection, rebase and squash, and history archaeology through blame, bisect and pickaxe.
g-doc-review
Documentation review gate. Dispatches the doc-reviewer agent on the changed file set to check documentation currency against the code it describes, then issues a standalone DOCS READY or DOCS HOLD verdict. On DOCS READY it writes the doc-approval sentinel that the commit gate checks for doc/mixed commits. Read-only on…
g-retro
Synthesize a session retrospective from the silent-observer journal — no interview. Reads the passive activity log (.claude/journal/), git history, and g-docs/todo.md, and writes g-docs/retros/YYYY-MM-DD-topic.md with what happened, decisions inferred, patterns, and cold-start context.
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
watch-pr
Watch an Elixir/Phoenix PR with an Amp Orb keep-alive lease until required non-deployment CI is green and review threads are resolved. Use after opening or updating a PR.