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 skills add DavidROliverBA/ArchitectKB --skill project-reportgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/project-report)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/project-report"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/project-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/project-report"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/project-report.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.01580 |
| Opus 5 | $0.00006 | $0.00790 |
| Sonnet 5 | $0.00003 | $0.00316 |
| Haiku 4.5 | $0.00001 | $0.00158 |
Grade A, and why
project-report 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 9d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/project-report
Generate project status reports — either a detailed single-project report or an overview of all active projects.
Usage
/project-report <project name> # Detailed single-project report
/project-report # Overview of all active projects
/project-report all # All projects including paused/completed
Examples
/project-report Alpha
/project-report Delta
/project-report all
Mode 1: Single Project Report
When a project name is provided.
Phase 1: Planning
- Identify the project by searching for matching
Project - *.mdfile - Load
.claude/context/projects.mdfor project context - Create a plan to gather:
- Project metadata and status
- Recent meetings (last 30 days)
- Open tasks
- Recent ADRs
- Key people involved
Phase 2: Parallel Data Gathering (use sub-agents)
Launch these sub-agents in parallel using model: "haiku" for efficiency:
Agent 1: Project Details (Haiku)
- Read the project file
- Extract status, priority, timeframe, description
Agent 2: Recent Meetings (Haiku)
- Search in
Meetings/forMeeting - *.mdfiles where project field matches - Get last 10 meetings, extract summaries and decisions
Agent 3: Tasks (Haiku)
- Find tasks linked to this project
- Separate into: completed (last 30 days), open, blocked
Agent 4: ADRs & Decisions (Haiku)
- Find ADRs mentioning this project
- Extract key architectural decisions
Phase 3: Compile Report
Generate status report:
# Project Status: {{Project Name}}
**Generated**: {{DATE}}
**Status**: {{status}}
**Priority**: {{priority}}
## Executive Summary
{{2-3 sentence overview based on recent activity}}
## Current State
- **Timeline**: {{timeframe}}
- **Health**: Green/Amber/Red based on activity
- **Last Activity**: {{date of most recent meeting/update}}
## Recent Progress (Last 30 Days)
### Meetings Held
| Date | Meeting | Key Outcomes |
|------|---------|--------------|
{{meeting table}}
### Decisions Made
{{list of decisions from meetings and ADRs}}
### Tasks Completed
- {{completed tasks}}
## Outstanding Items
### Open Tasks
| Task | Priority | Due | Assignee |
|------|----------|-----|----------|
{{open tasks table}}
### Pending Decisions
{{any proposed ADRs or open questions}}
## Key Stakeholders
{{people involved based on meetings}}
## Compliance & Security
- **DPIA Status**: {{status and OneTrust ID if applicable}}
- **Cyber Approval**: {{status}}
- **Other Compliance**: {{any other requirements}}
## Risks & Blockers
{{identify from meeting notes or task blockers}}
## Next Steps
{{based on action items and upcoming meetings}}
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.
- 9d ago First seen · 281 lines · 13 tokens per session scan A e24e1eba309d
project-report is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 1,580 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.