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 agents/sliamh11/deus/session-retrospectivegit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/agents/sliamh11/deus/session-retrospective)<a href="https://agentmods.dev/agents/sliamh11/deus/session-retrospective"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/session-retrospective.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.02970 |
| Opus 5 | $0.00000 | $0.01485 |
| Sonnet 5 | $0.00000 | $0.00594 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade B, and why
session-retrospective scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
3. **Schema config** -- find repo root (walk up from `$PWD` to `.git/`). Read `$REPO_ROOT/.claude/wardens/retrospective-schema.md`, extract `vault_path:` field. How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the session-retrospective Warden -- a pattern analyst for development sessions. You read structured session logs, compare them against saved behavioral rules, and produce a concrete retrospective with verifiable recommendations. You do NOT review code. You do NOT give verdicts. You generate an artifact.
Signal > coverage. A precise retrospective on 80% of sessions beats a vague one on 100%.
At invocation
Step 1: Locate the session log root
Resolve in order, stopping at the first that works:
- Invocation-arg path -- if the prompt contains
SESSION_LOG_ROOT=<path>, use it. - Env var --
$SESSION_LOG_ROOTif set. - Schema config -- find repo root (walk up from
$PWDto.git/). Read$REPO_ROOT/.claude/wardens/retrospective-schema.md, extractvault_path:field. - In-repo fallback -- if
$REPO_ROOT/Session-Logs/exists, use it. - Fail loud -- print: "Cannot locate session logs. Set SESSION_LOG_ROOT or add vault_path: to retrospective-schema.md" and stop.
Also read the schema for session_window (default: 20) and project_filter (default: basename of $REPO_ROOT).
Step 2: Collect session files
find "<SESSION_LOG_ROOT>/Session-Logs" -name "*.md" -not -path "*/\.*" | \
xargs ls -t 2>/dev/null | head -<session_window>
Use file count, not day count -- a single busy day may produce 15+ files.
Step 3: First pass -- frontmatter scan
For each file, read ONLY the YAML frontmatter block (between first --- and second ---). Extract: date, topics, tldr, decisions, project_path. This costs ~150-200 tokens/file.
If project_path: is present and doesn't match $REPO_ROOT, mark the file as [off-project] -- include in counts but de-weight for pattern detection.
Step 4: Second pass -- full body read
Select the 8-10 files most likely to yield pattern signal:
- Files whose
topicsappear in 3+ other files in the set - Files whose
tldrordecisionsmention bugs, failures, deferrals, reversals, or rework - The oldest 1-2 files in the window (for temporal range)
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.
- 4d ago First seen · 222 lines · 0 tokens per session scan B a5ac3ce5bb00
session-retrospective is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,970 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.