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 VoytechG/spec-driven-development --skill review-project-historygit clone --depth 1 https://github.com/VoytechG/spec-driven-developmentWrote 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/voytechg/spec-driven-development/review-project-history)<a href="https://agentmods.dev/skills/voytechg/spec-driven-development/review-project-history"><img src="https://agentmods.dev/badge/skills/voytechg/spec-driven-development/review-project-history.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.1 | $0.00036 | $0.00449 |
| Opus 5 | $0.00018 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
review-project-history 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 8d 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.
What it actually says
Review Project History
Retrieve historical context deliberately, then summarize only what matters for the
current question. This skill is the escape hatch for rich context; normal coding
work should use load-project-context instead.
Workflow
- Read
AREAS.mdat the project root. Match the prompt and paths to the relevant area entries. - Read the area's active entry points first:
<docsRoot>/README.md<docsRoot>/implementation-status.md, if present- the active
spec.md,product-spec.md, or named feature spec, if present
- Search history before reading it. Build a candidate list from history paths that actually exist, then run targeted search over that list. Likely paths include:
<docsRoot>/decisions/<docsRoot>/logs/<docsRoot>/archive/<docsRoot>/plans/<docsRoot>/specs/
- Read only relevant matches. Prefer one decision record or one archived plan over loading a whole folder. Do not pass missing paths to search commands. If matches are broad, summarize headings first and choose the smallest useful subset.
- Return a concise history summary:
- settled decisions that still apply;
- rejected alternatives and why they were rejected;
- stale or superseded material;
- open questions that remain unresolved;
- files worth reading next, if any.
- Do not update docs from this skill unless the user asks. If history should be promoted into active docs, recommend the smallest specific doc change.
When To Use
Use this for prompts like:
- "onboard me to this area";
- "why did we choose this?";
- "did we already consider this?";
- "review the old plans before we change it";
- "summarize the decision history."
Do not use it for routine coding context.
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.
- 8d ago First seen · 44 lines · 36 tokens per session scan A 82339b3c3986
review-project-history is a skill published in the GitHub repository VoytechG/spec-driven-development (4 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 449 once invoked, about $0.0002 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.