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 aget-framework/template-advisor-aget --skill aget-check-initiativegit clone --depth 1 https://github.com/aget-framework/template-advisor-agetWrote 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/aget-framework/template-advisor-aget/aget-check-initiative)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-check-initiative"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-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/aget-framework/template-advisor-aget/aget-check-initiative"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-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.00034 | $0.01511 |
| Opus 5 | $0.00017 | $0.00756 |
| Sonnet 5 | $0.00007 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
aget-check-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 11d 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.
This is a copy
100% identical to aget-check-initiative — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-check-initiative
Read-only cross-system coherence check for initiatives. Aggregates state across Systems of Record and the local KB, then reports alignment, drift, and gaps.
Purpose
Checking initiative state today requires manual queries across 3-4 systems. The principal must context-switch between Linear, GitHub, Slack, and KB to build a coherent picture. This skill composes those reads into a single report, answering: "What is the current state of initiative X across all systems?"
This is the first skill implementing the SoR Consumer Pattern (L759). It reads from external systems but never writes to them.
Evidence: L759 (SoR Consumer Pattern), L760 (Initiative as Scope Modifier), L747 (Event Awareness SLA), L665 (File-and-Route). SOP_initiative.md v1.2.0 channel registry (#916).
Input
$ARGUMENTS - Initiative name or ID
Examples:
/aget-check-initiative INIT-CORE-ARTIFACT-MATURATION— Check specific initiative by ID/aget-check-initiative voice framework— Check by name (fuzzy match)check initiative status— Check all active initiativeswhat's the state of the artifact maturation initiative?— Natural language trigger
Execution
Step 1: Resolve Initiative
Find the initiative manifest:
- Search
planning/initiatives/INIT-*.mdfor matching ID or name - If no match, search
planning/PROJECT_PLAN_*.mdfor initiative references - If still no match, report available initiatives and stop
Extract from the manifest:
- Initiative ID and name
- Stream list with expected status
- Channel registry (if
## Channelssection exists per SOP v1.1.0)
Step 2: KB State Scan
Read local KB artifacts linked to the initiative:
| Artifact Type | Search Pattern | Extract |
|---|---|---|
| PROJECT_PLANs | planning/PROJECT_PLAN_*{initiative}* |
Gate status, velocity |
| L-docs | initiative_id in metadata |
Count, latest date |
| Observations | .aget/research/OBSERVATION_* |
Count, unprocessed count |
| Design directions | docs/DESIGN_DIRECTION_* |
Status, version |
| Issues filed | Initiative label in issues | Open/closed counts |
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.
- 11d ago First seen · 148 lines · 34 tokens per session scan A ce849eb6e204
aget-check-initiative is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 1,511 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aget-check-initiative, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-control-center
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.
metagit-sharing-state
Configure shared coordination state (objectives, handoffs, approvals, events) across multiple agents and machines via METAGITSTATEURL, optional DynamoDB / MongoDB DocumentStore backends, and the ops HTTP path. Use when Hermes subagents, CI runners, or humans must see the same objective queue without Syncthing JSON…
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
metagit-aos
Compose ACL, task graph, scheduler, merge, and related coordination subsystems via metagit aos|coord status|doctor|next. Use when an operator or orchestrator needs one snapshot of coordination health or the next work envelope without launching models. Start with the day-1 quickstart for the canonical control loop.