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/lis186/sourceatlas/dev-notes-guidegit clone --depth 1 https://github.com/lis186/SourceAtlasWhat 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.00012 | $0.00419 |
| Opus 5 | $0.00006 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
dev-notes-guide 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
dev-notes/ Management Guide
File Naming Rules
UPPER_CASE.md (max 5 files)
Only for files that meet ALL criteria:
- Updated weekly
- Index/navigation purpose
- Long-term methodology
Current: README.md, HISTORY.md, KEY_LEARNINGS.md, ROADMAP.md, METHODOLOGY.md Never create new uppercase files without explicit approval.
YYYY-MM-DD-topic-type.md
For everything else:
topic: hyphen-separated (e.g.,objective-c-support)type: implementation | analysis | decision | test | experiment
Location Rules
if current/last month → dev-notes/YYYY-MM/
elif decision analysis → dev-notes/archives/decisions/
elif methodology deep-dive → dev-notes/archives/lessons/
else → dev-notes/YYYY-MM/ (matching month)
Must-Follow Rules
- Never create new UPPER_CASE files
- Always use date prefix for new content
- Update HISTORY.md immediately after major features
- Merge same-day + same-topic content
- Move 3+ month old content to archives/
Update Templates
HISTORY.md
### Week N (MM/DD-MM/DD): Topic
- **Feature** (MM/DD): One-line description → [Details](link)
KEY_LEARNINGS.md
### N. Learning Title
**Discovery**: 1 sentence
**Evidence**: 1 sentence
**Application**: 1 sentence
→ [Full analysis](link)
Information Layers
- Layer 0 (README.md): 10-sec overview
- Layer 1 (5 core files): 5-min understanding
- Layer 2 (monthly folders): 30-min details
- Layer 3 (archives/): Deep dive
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 · 63 lines · 12 tokens per session scan A bda20f89a4f5
dev-notes-guide is a command published in the GitHub repository lis186/SourceAtlas (46 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 419 once invoked, about $0.0001 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-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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.