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 ssmurfgg04-gif/context-m --skill team-okrsgit clone --depth 1 https://github.com/ssmurfgg04-gif/context-mWrote 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/ssmurfgg04-gif/context-m/team-okrs)<a href="https://agentmods.dev/skills/ssmurfgg04-gif/context-m/team-okrs"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/team-okrs/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/ssmurfgg04-gif/context-m/team-okrs"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/team-okrs.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.00072 | $0.01227 |
| Opus 5 | $0.00036 | $0.00613 |
| Sonnet 5 | $0.00014 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
team-okrs 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 8d 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 team-okrs — 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team OKRs Template
Use this template when the artifact is a team-facing status / OKR / sprint console — not a personal todo, not a public marketing page, not a deck.
Use When
- The audience is a team, lead, or stakeholder reviewing collective progress — quarterly OKR review, sprint status, "this week" all-hands view.
- Surfaces needed: sprint hero with progress segments, workstream cards with owners, chronological activity feed with event types (shipped / blocked / reviewed / commented / uploaded), today's schedule, team presence, upcoming milestones.
- Look should feel like a polished internal tool (Linear / Asana / Notion-flavored), neutral and calm.
Avoid When
- The artifact is a personal todo / planner — too team-centric.
- The artifact is meant to be presented as slides (use a
ppt/deck template). - The page is public marketing — wrong audience, wrong density.
- The data is purely analytical (charts, BI metrics) — use
dashboard/(more chart-oriented) instead. - The content is a periodic narrative digest with prose — use
Project Brief/(notebook weekly digest).
Required Reading
Read this SKILL.md first. Do not read activity-stream.html by default.
Read activity-stream.html only when you need: the 4-segment sprint progress bar geometry, the event-badge taxonomy (green check / red alert / purple comment / amber up-arrow / dark review), the workstream-card layout, the schedule current-time indicator, or the team-presence dot pattern. Extract patterns; do not copy placeholder names, project titles, or class names wholesale.
Design Strategy
Decide the page's answer before placing components:
- "Are we on track this sprint?" → hero progress + status stats dominate
- "What did the team do this week?" → activity stream is the spine, hero shrinks
- "What's next?" → workstream cards + milestones dominate
- "Who's around right now?" → presence + schedule dominate
A single page can blend these but pick the lead question.
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.
- 8d ago First seen · 92 lines · 72 tokens per session scan A 35151886f116
team-okrs is a skill published in the GitHub repository ssmurfgg04-gif/context-m (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 1,227 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to team-okrs, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
test-plan
Build a test plan when a new Epic is created. Pulls epic details and linked stories from Jira, analyzes scope, and produces a test plan covering strategy, automation gap analysis, success criteria, environment needs, and risks. Output goes to Confluence and local test knowledge base. Use when: "test plan", "plan tests…
review-ticket
Review a Jira ticket during backlog grooming or refinement. Audits the ticket for testability, AC completeness, missing edge cases, and potential blockers. Outputs a structured review the SDT can bring to the grooming session. Use when: "review this ticket", "check ACs", "testability review", "grooming". Do NOT use…
setup
First-run configuration wizard for QABuddy. Sets up context source (Jira, spec docs, chat, custom), team mode (solo vs PR-based), and project preferences. Writes .qabuddy.json to the project root. Optionally wires QABuddy to run on pull requests (the reusable PR-coverage workflow). Re-run to reconfigure. Use when…
digest
NOTE: this skill requires connected chat / email / project-tracker / docs MCPs, which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Cross-tool rollup of what's pending, what shipped, and what's blocked across chat / email / project tracker /…
roadmap
Render a per-project feature roadmap — a Band×Status grid (Shipped/Current/Next/Later × done/in-progress/blocked/buildable) synthesized from CLAUDE.md + PROGRESS.md, persisted to a committed ROADMAP.md with staleness-aware refresh. Modes: '/roadmap' (nearest project), '/roadmap ' (a projectslist tag), '/roadmap…
stitch
Build or verify cross-repo STITCH.md linking backend + frontends in a product group. Modes: create, verify, diff, section. Uses CODEMAPs as drift source by default. Trigger: '/stitch create ', '/stitch diff '.