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 tahirraufkeeyu/software-development-agent-stack--sdas --skill status-updategit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/status-update)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/status-update"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/status-update.svg" alt="Measured on agentmods" 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.00065 | $0.01891 |
| Opus 5 | $0.00032 | $0.00945 |
| Sonnet 5 | $0.00013 | $0.00378 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
status-update 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when:
- A team lead says "write up this week's status" or "draft the Friday update."
- It is the end of a sprint or milestone and a written rollup is needed for leadership, cross-functional partners, or an internal newsletter.
- A new stakeholder has been added and needs to be caught up on the last week or two.
Do not use this skill for:
- Personal/daily standup updates (use
engineering:standupinstead). - Incident-specific updates mid-incident (use
engineering:incident-response). - Customer-facing release notes (use
changelog).
Inputs
Required:
- Team name and reporting window (e.g., "Platform team, week of 2026-04-13").
- Access to one of: git repo(s), GitHub/GitLab MCP, project board (Linear/Jira/Asana) MCP, or a manually pasted export of tickets and PRs.
Optional:
- Previous week's status update (for continuity — the skill will check whether prior "next week" items actually shipped).
- List of cross-functional partners to address "asks" to.
- Metrics the team tracks weekly (e.g., p95 latency, signup conversion, open SEV2 count).
Outputs
A single Markdown document with the following sections, ~300 words total:
- Week of
<date>—<Team>header - TL;DR — one sentence
- Shipped — bullets with user/business impact, not feature names alone
- In flight — bullets with percent complete and ETA
- Next week — bullets, max 5
- Risks and blockers — each with a mitigation or an explicit "needs help"
- Asks — specific requests from named cross-functional partners
- Metrics (optional) — week-over-week deltas
Output is written to stdout by default. If a path is provided (e.g., a Notion page ID or a file path), the skill writes there.
Tool dependencies
- Read / Grep / Glob — for scanning local git repos and reading prior status docs.
- Bash —
git log,git shortlog,gh pr list --state merged --search "merged:>=...". - GitHub MCP (preferred) —
list_pull_requests,list_commitsfor richer metadata. - Linear MCP / Jira MCP / Asana MCP —
list_issuesfiltered by team and updated-at window. - Notion MCP (optional) — to read the prior week's update and write the new one.
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 · 135 lines · 65 tokens per session scan A e08891451590
status-update is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 1,891 once invoked, about $0.0003 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.