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 project-trackinggit 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/project-tracking)<a href="https://agentmods.dev/skills/saolalab/clawforce/project-tracking"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/project-tracking/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/project-tracking"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/project-tracking.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.00022 | $0.00360 |
| Opus 5.5 | $0.00009 | $0.00144 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
project-tracking 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.
What it actually says
Project Tracking
Status Report Template
## Project Status: [Date]
### Summary
[One paragraph overview]
### RAG Status: 🟢/🟡/🔴
### Progress
- Completed: [X]%
- On track: [Yes/No]
### Key Accomplishments
- Achievement 1
- Achievement 2
### Upcoming Milestones
| Milestone | Due Date | Status |
|-----------|----------|--------|
| ... | ... | ... |
### Risks & Issues
| Item | Impact | Mitigation |
|------|--------|------------|
| ... | ... | ... |
### Blockers
- Blocker 1: [Status/Owner]
### Next Week Focus
- Priority 1
- Priority 2
Agile Metrics
| Metric | Description | Target |
|---|---|---|
| Velocity | Points per sprint | Stable |
| Burndown | Work remaining | Linear |
| Cycle Time | Start to done | Decreasing |
| Escaped Defects | Bugs in prod | Zero |
Risk Management
Risk Register Fields
- ID
- Description
- Probability (1-5)
- Impact (1-5)
- Score (P × I)
- Mitigation
- Owner
- Status
Risk Response Strategies
- Avoid: Eliminate the threat
- Mitigate: Reduce probability/impact
- Transfer: Shift to third party
- Accept: Acknowledge and monitor
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 · 71 lines · 22 tokens per session scan A 4039e2d514e1
project-tracking is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 360 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.