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 comms-weeklygit 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/comms-weekly)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/comms-weekly"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/comms-weekly.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.00051 | $0.02367 |
| Opus 5 | $0.00026 | $0.01184 |
| Sonnet 5 | $0.00010 | $0.00473 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
comms-weekly 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this orchestrator when:
- The weekly leadership sync has concluded and a transcript is available.
- Someone says "run the comms week", "prep the weekly comms package", or "roll up this week's internal comms".
- It is Monday or Tuesday of a given workweek and the comms team needs the three-part bundle produced.
Do not use for:
- Ad-hoc incident comms (use incident-response comms patterns).
- Exec-to-exec memos that do not get distributed (use a direct draft, not this pipeline).
- Customer-facing comms (this is internal only; external announcements go through marketing or PR review).
Chained skills
In execution order:
meeting-notes— processes the leadership-sync transcript. Extracts decisions, action items, open questions. Writesleadership-notes.md.status-update— drafts the all-hands status update from the extracted decisions plus per-team bullets. Writesstatus-update.md.announcement— invoked only when a milestone, policy change, launch, org change, or customer-impacting decision is detected in step 1. Writesannouncement.md.
The orchestrator inspects decisions from step 1 against an announcement-trigger rubric (below) to decide whether to run step 3.
Inputs
Required:
- Week-of slug — ISO Monday date, e.g.
2026-04-13. - Leadership-sync transcript — file path, paste, or link (Otter, Granola, Fireflies, Meet).
- Team inputs — per-team bullets (shipped, in-flight, blocked) from team leads. Expected teams default to: Platform, Product, Design, Growth, Revenue, People, Finance. Override via
teamsinput.
Optional:
- Distribution list — default
all@company. Override for restricted-scope weeks. - Announcement audience — one of
all-employees,customers,both. Defaults toall-employees. - Publish timestamps — if not provided, uses Tuesday 16:00 local for status, announcement (if any) Thursday 09:00 local.
Outputs
A single Markdown bundle at comms/weekly/<week-of>-package.md, containing:
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 · 157 lines · 51 tokens per session scan A e3ed3e2a30ba
comms-weekly is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 2,367 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.