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 saajunaid/caddis-plugin --skill internal-commsgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/internal-comms)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/internal-comms"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/internal-comms/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/saajunaid/caddis-plugin/internal-comms"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/internal-comms.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.00027 | $0.00684 |
| Opus 5.5 | $0.00011 | $0.00274 |
| Sonnet 5.5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
internal-comms 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 19d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal Communications
Document Types
Status Report
# [Project Name] Status Report
**Date:** [Date]
**Author:** [Name]
**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked
## Summary
[2-3 sentence overview]
## Progress This Week
- Completed: [items]
- In Progress: [items]
- Blocked: [items with owners]
## Key Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric] | [Target] | [Actual] | ⬆️/➡️/⬇️ |
## Next Week
- [Planned items]
## Risks & Mitigations
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| [Risk] | H/M/L | [Action] | [Name] |
## Asks
- [Any blockers needing escalation]
Leadership Update
# [Team] Update - [Date]
## TL;DR
[One paragraph executive summary - the only thing busy execs will read]
## Wins
- [Key accomplishment with impact]
- [Key accomplishment with impact]
## Challenges
- [Challenge]: [What we're doing about it]
## Key Decisions Needed
1. [Decision]: [Context, options, recommendation]
## Metrics Dashboard
[Include 3-5 key metrics with trends]
Incident Report
# Incident Report: [Title]
**Severity:** P0/P1/P2/P3
**Duration:** [Start] - [End]
**Impact:** [User/revenue impact]
**Status:** Resolved/Monitoring/Active
## Timeline
| Time (UTC) | Event |
|------------|-------|
| [Time] | [What happened] |
## Root Cause
[Clear explanation of what went wrong]
## Resolution
[What was done to fix it]
## Action Items
| Item | Owner | Due Date | Status |
|------|-------|----------|--------|
| [Action] | [Name] | [Date] | ⬜/✅ |
## Lessons Learned
- [What we learned]
- [What we'll do differently]
All-Hands Announcement
# [Announcement Title]
Hey team,
[Opening that sets context]
**What's happening:** [Clear, simple explanation]
**Why it matters:** [Impact and benefits]
**What you need to do:** [Specific actions if any]
**Timeline:**
- [Date]: [Milestone]
- [Date]: [Milestone]
**Questions?** [Where to ask]
[Sign-off]
What ships with it
5 files 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.
- 19d ago Changed · -9 tokens per session 11145a1f41bf
- 1mo ago First seen · 125 lines · 36 tokens per session scan A b89263a06241
internal-comms is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 684 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-09-03.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-discover
Interview the user relentlessly about a decision until every branch of the design tree is resolved, then record the result as a short ADR.