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 saolalab/clawforce --skill roadmapgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/roadmap)<a href="https://agentmods.dev/skills/saolalab/clawforce/roadmap"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/roadmap/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/saolalab/clawforce/roadmap"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/roadmap.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.00037 | $0.00990 |
| Opus 5.5 | $0.00015 | $0.00396 |
| Sonnet 5.5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
roadmap 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Roadmap Management
Roadmap Template (Now/Next/Later)
# Product Roadmap — Q{N} {YEAR}
## Now (This Quarter)
- **Feature 1**: {Brief description} — {Target launch date}
- **Feature 2**: {Brief description} — {Target launch date}
- **Feature 3**: {Brief description} — {Target launch date}
## Next (Next Quarter)
- **Feature 4**: {Brief description} — {Rationale}
- **Feature 5**: {Brief description} — {Rationale}
## Later (Future Exploration)
- **Feature 6**: {Brief description} — {Research needed}
- **Feature 7**: {Brief description} — {Research needed}
Feature Specification Template (PRD)
# Feature: {Feature Name}
## Problem Statement
- **User Problem**: {What problem are users facing?}
- **Business Problem**: {Why does this matter to the business?}
- **Evidence**: {Data, user quotes, research that supports this}
## Hypothesis
If we {build this feature}, then {expected outcome}, because {reasoning}.
## Solution
- **Overview**: {High-level description of the solution}
- **User Stories**:
- As a {user type}, I want {action}, so that {benefit}
- As a {user type}, I want {action}, so that {benefit}
- **Key Features**: (bulleted list)
- **Design Considerations**: {Notes for design team}
## Success Metrics
- **Primary Metric**: {Metric name} — Target: {target value}
- **Secondary Metrics**:
- {Metric name}: {target}
- {Metric name}: {target}
- **How we'll measure**: {Data sources, analytics events}
## Edge Cases & Considerations
- {Edge case 1}: {How we'll handle it}
- {Edge case 2}: {How we'll handle it}
- **Technical Constraints**: {Any known limitations}
- **Dependencies**: {Other features or systems needed}
## Launch Plan
- **Beta**: {Date and user group}
- **Full Launch**: {Date}
- **Rollout Strategy**: {Gradual rollout? Feature flag?}
- **Marketing**: {Key messages and channels}
- **Support**: {Documentation, training needed}
RICE Scoring Template
## Feature Prioritization — RICE Scoring
| Feature | Reach | Impact | Confidence | Effort | Score | Rank |
|---------|-------|--------|------------|--------|-------|------|
| Feature A | {users/quarter} | {0.25-3} | {50-100%} | {person-months} | {calculated} | 1 |
| Feature B | {users/quarter} | {0.25-3} | {50-100%} | {person-months} | {calculated} | 2 |
**Scoring Guide**:
- **Reach**: Users affected per quarter
- **Impact**: 0.25 = minimal, 0.5 = low, 1 = medium, 2 = high, 3 = massive
- **Confidence**: 50% = low, 80% = medium, 100% = high
- **Effort**: Person-months (minimum 0.5)
- **Score**: (Reach × Impact × Confidence) / Effort
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 · 110 lines · 37 tokens per session scan A b44b1c389d9a
roadmap is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 990 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-08-30.
Other skills, from other repositories
03_task6
A workflow for collecting Slack messages from different departments and preparing a board-level execution-summary draft for an executive.
03_task4
Reads recent Slack messages to compile an accurate project status report and saves it as a draft for review before sending to a client. Use when: preparing a client-facing update, reconciling conflicting or revised numbers from multiple sources, or drafting a message that requires human review before sending.
03_task5
Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.
03_task2
Extracts action items and pending tasks from Slack messages. Use when: reviewing unread messages for todos, finding deadlines or requests directed at the user, or producing a task summary from recent Slack activity.
03_task1
Coordinates meeting scheduling via Gmail and Calendar APIs. Use when: scheduling a meeting, checking participant availability, sending coordination emails, creating calendar events, or notifying organizers of confirmed bookings.
meeting-to-action
Convert meeting notes or transcripts into clear summaries, decisions, and action items with owners and due dates. Use when a user asks to turn a meeting recording, transcript, or notes into a follow-up plan.