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 commands/chhuax/praxis-devos/devos-docs-initgit clone --depth 1 https://github.com/chhuax/praxis-devosWhat 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.00000 | $0.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
devos-docs-init 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 2d 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.
What it actually says
devos-docs-init
Initialize project documentation using the devos-docs skill.
What this does
- Generates
docs/surfaces.yaml - Generates
docs/codemaps/project-overview.md - Uses deterministic validation before writeback
Mode
init
How to use
Run this command when:
- setting up docs for the first time
- the project structure has changed significantly
Implementation
- Invoke the
devos-docsskill withmode=init - Detect the project's language preference and pass it as
artifact_language:- First check existing
docs/surfaces.yamlfor anartifact_languagefield - Otherwise infer from the primary language of
AGENTS.md/README.md - Pass the detected value to the
devos-docsskill; if no preference is found, omit (defaults toen)
- First check existing
- If using a sub-agent for repository exploration, follow the Agent Collaboration protocol in the
devos-docsskill — the sub-agent prompt must request the standard exploration return structure (adapted for the project's language/build system) and prohibit writing to external files - The main agent must consume the sub-agent's return; discarding it and rebuilding from scratch is a protocol violation
- Use the stable docs routing order:
docs/surfaces.yamldocs/codemaps/project-overview.mddocs/codemaps/module-map.mdonly for multi-module projectsdocs/codemaps/modules/<artifactId>.mdonly when module routing is deterministic
- Before writing any file, complete contract assembly and validation (see Validation Contract in the
devos-docsskill) — writing files without a validated contract is a protocol violation - Write all files in a single pass after validation; writing files incrementally during exploration is prohibited
- Canonical paths:
docs/surfaces.yamldocs/codemaps/**
Notes
- This is a thin wrapper. Core logic lives in the
devos-docsskill. - No CLI fallback is provided; use the projected host command or invoke the
devos-docsskill directly.
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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A d71e65e52302
devos-docs-init is a command published in the GitHub repository chhuax/praxis-devos (21 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 460 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.