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 jukrap/ai-agent-playbook --skill project-notesgit clone --depth 1 https://github.com/jukrap/ai-agent-playbookWrote 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/jukrap/ai-agent-playbook/project-notes)<a href="https://agentmods.dev/skills/jukrap/ai-agent-playbook/project-notes"><img src="https://agentmods.dev/badge/skills/jukrap/ai-agent-playbook/project-notes/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/jukrap/ai-agent-playbook/project-notes"><img src="https://agentmods.dev/badge/skills/jukrap/ai-agent-playbook/project-notes.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.00015 | $0.00229 |
| Opus 5.5 | $0.00006 | $0.00092 |
| Sonnet 5.5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
project-notes 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 29d 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 Notes
Use the project's existing current-state entrypoint and read only the evidence relevant to the task. Keep the active objective, constraints, verified state, next action, and useful links concise. Follow existing formats; do not create a parallel record system or log every response.
At meaningful milestones, update the existing records with decisions and checks actually performed. Distinguish intended behavior, observed results, and unknowns. Preserve prior evidence, user edits, and local-only rules; keep secrets out of records. In a shared workspace, select an explicitly registered repository before code or Git operations; shared notes do not authorize changes across repositories.
Keep replies and deliverables focused on the work, results, and limitations. Omit unsolicited workflow branding and skill-name narration. Answer direct questions about methods truthfully and follow required disclosures and attribution. This guidance does not change permissions, audit records, or host instructions.
Use the host's existing tools. Read additional guidance only when the task requires it; this skill has no reference bundle or required companion skills.
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.
- 29d ago First seen · 15 lines · 15 tokens per session scan A 523e93e0e1d3
project-notes is a skill published in the GitHub repository jukrap/ai-agent-playbook (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 229 once invoked, about $0.0001 per session on Opus 5.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-20.
Other skills, from other repositories
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
factory-human-digest
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
factory-collect
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.