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 announcementgit 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/announcement)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/announcement"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/announcement/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/tahirraufkeeyu/software-development-agent-stack--sdas/announcement"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/announcement.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.00056 | $0.02511 |
| Opus 5 | $0.00028 | $0.01256 |
| Sonnet 5 | $0.00011 | $0.00502 |
| Haiku 4.5 | $0.00006 | $0.00251 |
Grade A, and why
announcement 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 9d 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 — 202 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 product launch, feature GA, or deprecation needs an announcement.
- A milestone has been reached (customer count, revenue, hiring, anniversary) and leadership wants to share it.
- A policy change (holiday closure, new tool rollout, process update) needs to be communicated to employees.
- A customer-facing change (pricing, TOS, service window) requires a heads-up.
Do not use this skill for:
- Incident updates — use
incident-reportorengineering:incident-response. - Routine status updates — use
status-update. - Marketing campaigns with external budget and funnel implications — those require the marketing team.
Inputs
Required:
- Announcement type — one of:
launch,milestone,policy-change. - Topic / subject — what is being announced.
- Audience —
employees,customers,partners, orpublic. - Tone —
formalorcasual. (Default:casualfor employees,formalfor customers/partners/public unless overridden.)
Optional:
- Effective date (for policy changes and launches).
- Channel — Slack, email, blog, changelog entry — affects length and formatting.
- Signer — the person or team the announcement is from.
- Supporting links — documentation, FAQ, demo video, blog post.
- Prior related announcements — for continuity.
Outputs
A single Markdown draft. Structure depends on announcement type:
Launch:
- Hook (one sentence that names the thing and the outcome).
- What changed (concrete, specific).
- Why it matters (user or business benefit).
- Call to action (try it, read more, opt in).
Milestone:
- Specific number or achievement.
- Short story (what got us here).
- Thanks (to people, teams, or customers who made it possible).
- Call to action (optional — celebrate, share, keep going).
Policy change:
- What is changing.
- When (effective date).
- Why (the reason, honestly stated).
- Impact (what each audience needs to do).
- FAQ (3–5 anticipated questions).
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.
- 9d ago First seen · 202 lines · 56 tokens per session scan A 553b035fb94b
announcement is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 2,511 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…