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/cassler/awesome-claude-code-setup/dev-diarygit clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWhat 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.00306 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
dev-diary 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
Developer Diary Entry
Create a developer diary entry in /docs/developer-diary/ that captures your personal insights about the current work.
Entry Structure
-
Date & Context
- Today's date and entry number
- What you're currently working on
- Related issues or PRs
-
Technical Observations
- Interesting patterns or anti-patterns discovered
- Clever solutions you found or created
- Technical debt noticed
- Performance considerations
-
Personal Insights
- "Aha!" moments during development
- Frustrations and how you overcame them
- Things that surprised you
- Questions that arose during work
-
Future Considerations
- Ideas for improvements
- Potential refactoring opportunities
- Features that would be nice to have
- Architectural thoughts
-
Human Touch
- Your opinion on the code quality
- What made you smile or laugh
- Shower thoughts about the project
- Analogies or metaphors that help explain complex parts
Guidelines
- Be authentic and show personality
- Include code snippets if they illustrate a point
- Don't hold back on constructive criticism
- Share both successes and struggles
- Think of it as a letter to future developers (including yourself)
Remember: This is your space to be reflective, creative, and human. It's not just about what you did, but how you felt about it and what you learned.
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 · 44 lines · 0 tokens per session scan A 87c2e267cf9e
dev-diary is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 306 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
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.
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.