Borrowing it
Nothing to install: this file belongs to schmitthub/clawker. 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/schmitthub/clawker/main/.agents/skills/initiative/SKILL.mdgit clone --depth 1 https://github.com/schmitthub/clawkerWrote 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/schmitthub/clawker/initiative)<a href="https://agentmods.dev/skills/schmitthub/clawker/initiative"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/initiative/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/schmitthub/clawker/initiative"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/initiative.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.00043 | $0.01106 |
| Opus 5.5 | $0.00017 | $0.00442 |
| Sonnet 5.5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
initiative 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initiative
Plan work in a shared memory, then complete one task per conversation. Use the user's request to select planning or execution. Creating a plan does not start its implementation. Follow the active session's permissions and mode; in a read-only planning session, present the plan without writing memory or code.
Create a plan
- Read the project instructions, relevant code, and existing plans. Establish the intended result, scope, constraints, and measurable completion criteria. State assumptions and ask about choices that affect the work.
- Divide the work into tasks small enough to complete and verify in one conversation. Give each task its dependencies, affected files or modules, implementation steps, and acceptance checks with expected results. Follow the project's test-first requirements for code changes.
- Use assets/initiative.md to create the memory. Replace all placeholders, omit unused optional fields, and repeat the task section as needed. Retain shared context once: background, key files, design choices, and links to applicable instructions.
- Follow
.serena/memories/memory_maintenance.md. Unless the user supplies a location, useplans/<initiative-name>/initiativeas the memory name. Link it from the relevant parent memory, orplans/corefor a top-level plan, using amem:reference with a short description. Preserve existing records; do not overwrite another initiative with the same name. - Use Serena memory tools when available. Otherwise read and write the same
files under
.serena/memories/, adding.mdto the memory name. Report the memory name and provide a prompt to start the first task.
Continue a task
- Read the initiative memory and its linked instructions. Check the current branch, working tree, and relevant code before relying on recorded progress. Preserve unrelated edits and do not switch branches over existing work.
- Use the task named by the user. If none is named, resume an unfinished task already in progress; otherwise select the first pending or blocked task whose dependencies are complete. Recheck its blocker before resuming. If it still needs user input, or several tasks are already in progress, report the choice needed before editing. Do not bypass an incomplete dependency to start a requested task.
- Mark the task
in_progressand record the current agent. Implement only that task and changes needed to satisfy its acceptance criteria. If new evidence requires a scope decision, record it and ask before expanding work. - Run the task's acceptance checks. Record commands, results, and any checks that could not run. Fix failures within scope and rerun affected checks. A failed or unrun required check prevents completion.
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.
- 1mo ago First seen · 87 lines · 43 tokens per session scan A 35a28b64aa26
initiative is a skill published in the GitHub repository schmitthub/clawker (58 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,106 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-09-08.
Other skills, from other repositories
tasks
Manage Prismer workspace tasks across the full Kanban lifecycle — create, list, inspect, update, complete, approve, reject, cancel. Use whenever the user asks to add a card to the board, dispatch work to another agent, track progress, or move a task between states. Executes via the cloud task CLI.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
prismer-notion
Notion API + ntn CLI: pages, databases, markdown, Workers.
doc-sync
Before merge, mechanize Documentation-First — derive the code delta from git diff, then verify required docs are in sync (CHANGELOG, docs/api, CLAUDE.md/ROADMAP). Any SDK-package change must carry a matching CHANGELOG entry + aligned version files. A change that skipped a required doc is flagged as a gap; a…
spec-intake
Turn one atomic feature/gap request into a dispatchable task in a single pass — create the task, write SPEC.md (auto-folded into linkedAssetIds server-side), add acceptance criteria, record provenance. Two-part epics are refused, not silently split.
prismer-teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.