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/thelobbi/claude/doc-loggit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/commands/thelobbi/claude/doc-log)<a href="https://agentmods.dev/commands/thelobbi/claude/doc-log"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/doc-log.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.00000 | $0.01650 |
| Opus 5 | $0.00000 | $0.00825 |
| Sonnet 5 | $0.00000 | $0.00330 |
| Haiku 4.5 | $0.00000 | $0.00165 |
Grade A, and why
doc-log 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Logging Command
Manually log documentation creation or updates to the tracking system.
Command Metadata
```yaml command: doc-log description: Manually log documentation activity to orchestration database category: documentation priority: medium ```
Usage
```bash
Log documentation creation
/doc-log --file docs/setup.md --action created --summary "Initial setup guide"
Log documentation update
/doc-log --file README.md --action updated --summary "Added installation instructions"
Auto-sync to Obsidian
/doc-log --file docs/api.md --action created --sync
Specify document type
/doc-log --file custom-doc.md --type guide --action created ```
Parameters
| Parameter | Required | Description | Default |
|---|---|---|---|
--file |
Yes | Path to documentation file | - |
--action |
Yes | Action: created, updated, deleted | - |
--type |
No | Document type (readme, adr, guide, etc.) | Auto-detected |
--summary |
No | Brief summary of changes | - |
--sync |
No | Auto-sync to Obsidian vault | false |
--agent-id |
No | Agent ID (auto-detected if not provided) | Current agent |
--task-id |
No | Task ID (auto-detected if not provided) | Current task |
Document Types
Supported documentation types:
readme- README filesadr- Architecture Decision Recordsguide- User/developer guidesreference- Reference documentationresearch- Research notesapi- API documentationarchitecture- Architecture documentationquickstart- Quick start guidesintegration- Integration guides
Examples
Log New Documentation
```bash
/doc-log
--file docs/deployment/k8s-setup.md
--action created
--type guide
--summary "Kubernetes deployment guide for production"
--sync
```
Output: ``` ✓ Documentation logged successfully
File: docs/deployment/k8s-setup.md Type: guide Action: created Summary: Kubernetes deployment guide for production Lines: 156 Words: 1,234
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 · 269 lines · 0 tokens per session scan A 883f51f6637b
doc-log is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,650 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-31.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.