Borrowing it
Nothing to install: this file belongs to sandovaldavid/kioku. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sandovaldavid/kioku/main/.agents/skills/kioku-project-workflow/SKILL.mdgit clone --depth 1 https://github.com/sandovaldavid/kiokuWrote 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/sandovaldavid/kioku/kioku-project-workflow)<a href="https://agentmods.dev/skills/sandovaldavid/kioku/kioku-project-workflow"><img src="https://agentmods.dev/badge/skills/sandovaldavid/kioku/kioku-project-workflow/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/sandovaldavid/kioku/kioku-project-workflow"><img src="https://agentmods.dev/badge/skills/sandovaldavid/kioku/kioku-project-workflow.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.00039 | $0.01646 |
| Opus 5 | $0.00019 | $0.00823 |
| Sonnet 5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
kioku-project-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kioku project workflow
Use this skill to turn a project request into a deliberate repository-and-vault workflow. Kioku provides project memory, guarded Markdown writes, sessions, and optional coordination. The client remains responsible for repository inspection, code changes, tests, Git operations, and external services.
Inputs
Extract:
project: the exact Kioku project identifier returned bylist_projectsor stored in the project MOCproject:field.task: the requested outcome, constraints, acceptance criteria, repository, and target branch when known.
Do not derive a vault path from owner/repository, a similarly named folder, or prior convention. When the identifier is missing or ambiguous, call list_projects, inspect the relevant MOC, and resolve the project before writing.
Workflow
1. Discover capabilities and load context
For project work:
- Confirm the active repository and target branch with the client's repository tools.
- Call
get_server_capabilitieswhen optional groups or coordination may be needed. - Call
get_project_context(project=...)before editing code or project notes. - Read only relevant context, normally in this order:
- project MOC and latest session handoff;
- approved/current specs, active plans, and open bugs;
- relevant ADRs, tickets, backlog items, and knowledge notes.
- Inspect the source repository's current code, tests, contracts, configuration, documentation, issues, and pull requests. Vault context is not a substitute for source evidence.
Treat approved specs as current durable requirements. Draft specs are in progress; superseded and discarded specs are historical and must not be silently treated as current instructions.
Respect .kioku/config.yml folder roles, exclusions, templates, and capability policy. Do not invent local paths, credentials, or unavailable capability groups.
2. Classify the request
Choose the smallest workflow that preserves useful context:
| Request | Default action |
|---|---|
| Explanation, lookup, or status | Read/search only; no session or vault write |
| Feature/design needing durable behavior requirements | Create or update a first-class spec; create an implementation plan from that spec when execution begins |
| Multi-step implementation with no durable design gap | Start a session; create/update a plan when it helps execution |
| Bug investigation or fix | Start a session; record a bug only when root cause and evidence are reusable |
| Architecture choice | Read existing ADRs; record a proposed ADR before treating the decision as accepted |
| Reusable verified lesson | Save project knowledge after validation |
| Deferred improvement | Add a backlog item rather than expanding scope |
| Documentation synchronization | Separate current public repository truth from private reasoning and handoff 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.
- 10d ago First seen · 146 lines · 39 tokens per session scan A 0f8fef03fe9e
kioku-project-workflow is a skill published in the GitHub repository sandovaldavid/kioku (0 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 1,646 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
find-contact
A contact and company lookup for amoCRM, a customer-management system. It searches existing records, checks for duplicates, and can create a new contact or company with notes and related activity.
pipeline-report
A procedure for reporting the state of an amoCRM sales funnel, a set of stages that deals move through before they are won or lost. It groups deals by stage and value and checks how long they have been inactive.
unsorted-triage
A workflow for sorting new incoming requests in amoCRM, a customer-management system. It checks for duplicates, turns a request into a sales deal, records its context, and assigns a follow-up task.
complete-task
A workflow for completing or reassigning ELMA365 business-process tasks. ELMA365 is a business process management system in which tasks move a process from one step to the next.
applicant-search
A read-only workflow for finding a candidate in HuntFlow and reviewing their résumé. HuntFlow is a recruiting system that stores candidate records, hiring stages, tags, and attached résumés.
vacancy-funnel
A recruitment funnel analysis workflow for HuntFlow, a service for tracking job candidates through hiring stages. It gathers all candidates for a vacancy and measures movement, drop-offs, rejection reasons, recruiters, and candidate sources.