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 TimoBakx/ai-journaling-template --skill add-projectgit clone --depth 1 https://github.com/TimoBakx/ai-journaling-templateWrote 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/timobakx/ai-journaling-template/add-project)<a href="https://agentmods.dev/skills/timobakx/ai-journaling-template/add-project"><img src="https://agentmods.dev/badge/skills/timobakx/ai-journaling-template/add-project/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/timobakx/ai-journaling-template/add-project"><img src="https://agentmods.dev/badge/skills/timobakx/ai-journaling-template/add-project.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.00045 | $0.00901 |
| Opus 5.5 | $0.00018 | $0.00360 |
| Sonnet 5.5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
add-project 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 17d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Project
Workflow for creating a project file in projects/, connecting it to external tools and recording the working agreements.
When
- The user starts a new project or engagement
- The user wants to document an existing (ongoing) project after all
- The user explicitly asks to add a project
Steps
1. New or existing?
First ask explicitly: is this a new project (we are starting the engagement now) or an existing project (it is already running and we are recording it after all)?
This mainly determines how step 5 (working agreements) is filled in:
- New: we shape the working agreements together, before the engagement really starts.
- Existing: we record which working agreements already exist, so the coach can remind the user of them later.
2. Purpose & basic details
- Project name (and the file name in kebab-case, e.g.
new-client.md) - Purpose: what is the software trying to solve? The core of why this project exists.
- Type: web application, API, plugin, etc.
- Involvement: since when, in which role
- Status: ongoing, new, on hold, etc.
3. People
- Team members: who from the user's own organization is on it and in which role, plus the user's own role. (Colleagues have a file in
people/.) - Contacts (client): the external stakeholders: name, role, and how the collaboration goes. These belong under the
## External Contactssection in the project file, not inpeople/.
4. Sensitive data (optional)
If the organization works with ISO, the GDPR or comparable frameworks, ask explicitly: does this project process sensitive information? (yes/no). If yes: briefly note what kind (personal data, client data, credentials). This is a flag, not a full analysis, but something that has to be visible as soon as the project comes up in that context.
5. Working agreements (Way of Work)
These agreements are reference information the coach uses to remind the user of things later when the project is discussed. So record them for new and existing projects alike. Clear agreements at the start of an engagement prevent most of the trouble later.
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.
- 17d ago First seen · 75 lines · 45 tokens per session scan A b04fe408f939
add-project is a skill published in the GitHub repository TimoBakx/ai-journaling-template (34 stars, last pushed 18d ago), licensed MIT. It adds 45 tokens to every session and 901 once invoked, about $0.0002 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-10-15.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…