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 patleeman/neon-pilot --skill project-recap-artifactgit clone --depth 1 https://github.com/patleeman/neon-pilotWrote 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/patleeman/neon-pilot/project-recap-artifact)<a href="https://agentmods.dev/skills/patleeman/neon-pilot/project-recap-artifact"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/project-recap-artifact/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/patleeman/neon-pilot/project-recap-artifact"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/project-recap-artifact.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.00050 | $0.00387 |
| Opus 5 | $0.00025 | $0.00193 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
project-recap-artifact 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 10d 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
Project Recap Artifact
Create a concise visual recap that helps someone re-enter a project with the current state, decisions, open work, and next actions in one place.
Workflow
- Gather the relevant project state from the conversation, workspace status, referenced docs, and user-provided scope.
- Prefer confirmed facts and label uncertain or inferred items clearly.
- Read
../artifacts/references/visual-explainer-defaults.mdand use thetechnical-reportpreset. - Use
../../templates/visual-explainer.htmlas the HTML starting point when helpful. - Save through the
artifacttool with the metadata below.
Metadata Defaults
{
"action": "save",
"kind": "html",
"artifactType": "project-recap",
"stylePreset": "technical-report",
"templateVersion": "visual-explainer-v1",
"source": {
"kind": "command",
"command": "project-recap"
}
}
Add source.paths for project files or docs used as recap sources.
Artifact Shape
- Start with status, current objective, and what changed recently.
- Include decisions made, evidence, open questions, risks, and recommended next actions.
- Use a compact timeline or status table when it improves scanning.
- Avoid inventing certainty; mark assumptions and missing context.
- Preserve user style overrides in
styleOverrideswhile keeping the recap calm and readable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 43 lines · 50 tokens per session scan A d7e7d26cbcc5
project-recap-artifact is a skill published in the GitHub repository patleeman/neon-pilot (23 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 387 once invoked, about $0.0003 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.