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/michael-harris/devteam/devteam-logsgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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.01842 |
| Opus 5 | $0.00000 | $0.00921 |
| Sonnet 5 | $0.00000 | $0.00368 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
devteam-logs 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam Logs Command
Command: /devteam:logs [options]
View execution logs, event history, and debugging information.
Usage
/devteam:logs # Show recent logs
/devteam:logs --session <id> # Show logs for specific session
/devteam:logs --agent <name> # Filter by agent
/devteam:logs --level error # Filter by log level
/devteam:logs --tail 50 # Show last 50 entries
/devteam:logs --export # Export logs to file
Options
| Option | Description |
|---|---|
--session <id> |
Filter by session ID |
--agent <name> |
Filter by agent name |
--level <level> |
Filter by level: debug, info, warn, error |
--tail <n> |
Show last N entries (default: 20) |
--since <time> |
Show logs since time (e.g., "1h", "30m") |
--export |
Export to logs/devteam-TIMESTAMP.log |
--json |
Output as JSON |
--verbose |
Show full log details |
Your Process
Step 1: Query Events Database
async function getLogs(options) {
let query = `
SELECT
e.id,
e.timestamp,
e.event_type,
e.data,
s.command as session_command,
ar.agent
FROM events e
LEFT JOIN sessions s ON e.session_id = s.id
LEFT JOIN agent_runs ar ON e.session_id = ar.session_id
WHERE 1=1
`
const params = []
if (options.session) {
query += ` AND e.session_id = ?`
params.push(options.session)
}
if (options.agent) {
query += ` AND ar.agent LIKE ?`
params.push(`%${options.agent}%`)
}
if (options.level) {
query += ` AND json_extract(e.data, '$.level') = ?`
params.push(options.level)
}
if (options.since) {
const sinceTime = parseTimeOffset(options.since)
query += ` AND e.timestamp > datetime('now', ?)`
params.push(sinceTime)
}
query += ` ORDER BY e.timestamp DESC LIMIT ?`
params.push(options.tail || 20)
return await db.all(query, params)
}
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 · 242 lines · 0 tokens per session scan A b35b8d312a13
devteam-logs is a command published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,842 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
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
map
View, rebuild, or query the codebase dependency map.
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
code-explain
Explain complex code through clear narratives and visual diagrams.
health
Run documentation health checks (freshness, links, drift, cross-doc consistency).