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 skills/itsribbz/godspeed/sitrepnpx skills add itsribbZ/Godspeed --skill sitrepgit clone --depth 1 https://github.com/itsribbZ/GodspeedWrote 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/skills/itsribbz/godspeed/sitrep)<a href="https://agentmods.dev/skills/itsribbz/godspeed/sitrep"><img src="https://agentmods.dev/badge/skills/itsribbz/godspeed/sitrep.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.00056 | $0.00749 |
| Opus 5 | $0.00028 | $0.00375 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade C, and why
sitrep scanned grade C with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find ~/.claude/projects -maxdepth 3 -name "project_status.md" 2>/dev/null Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
for skill in $(ls -d ~/.claude/skills/*/); do How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sitrep — Cross-Project Status
Triggers: "sitrep", "status", "what's the state of everything", "where am I on stuff"
What it does
Scans ~/.claude/projects/*/memory/ for any file matching project_status.md (or project_*_status.md). For each one found:
- Read the most recent
## Session:entry - Extract the date and one-line summary
- Compute staleness bucket: Fresh (< 3 days), Idle (3-7), Stale (7-14), Dormant (14+)
- Flag any "blocked" or "in-progress" items with no resolution
Aggregates into a single dashboard.
Protocol
# 1. Discover projects
find ~/.claude/projects -maxdepth 3 -name "project_status.md" 2>/dev/null
# 2. For each, read the latest session entry + compute staleness
# (use head / grep / date arithmetic — no external deps)
# 3. Check learning pipeline health
for skill in $(ls -d ~/.claude/skills/*/); do
name=$(basename "$skill")
count=$(grep -c '^###' "$skill/_learnings.md" 2>/dev/null || echo 0)
# Flag any skill with <5 entries after 10+ invocations
done
# 4. Brain telemetry glance
wc -l ~/.claude/telemetry/brain/decisions.jsonl 2>/dev/null
cat ~/.claude/telemetry/brain/godspeed_count.txt 2>/dev/null
Output format
═══════════════════════════════════════════════════
SITREP — <date>
═══════════════════════════════════════════════════
PROJECTS (ranked by recency)
[Fresh] <project-slug> <date> <one-line summary>
[Idle] <project-slug> <date> <one-line summary>
[Stale] <project-slug> <date> <one-line summary>
[Dormant] <project-slug> <date> <one-line summary>
BLOCKERS (across all projects)
- <project>: <item flagged as blocked>
LEARNING PIPELINE
Skills with <5 entries after 10+ invocations: [list]
Staleness: [N] entries >60 days without confirmation
BRAIN
Decisions logged: <N>
Godspeed tick: <N>
WHAT NEEDS ATTENTION
1. <highest-priority item with reasoning>
2. <next>
3. <next>
═══════════════════════════════════════════════════
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 · 88 lines · 56 tokens per session scan C 31a62a0734ef
sitrep is a skill published in the GitHub repository itsribbZ/Godspeed (1 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 749 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
pilot
One autonomous Pilot cycle - fetch the agenda, execute the top item, journal, exit. Injected by the terminal host - not for manual invocation loops.