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 agentmods add skills/jamestorrevillas/dev-skills/internal-commsnpx skills add jamestorrevillas/dev-skills --skill internal-commsgit clone --depth 1 https://github.com/jamestorrevillas/dev-skillsWrote 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/jamestorrevillas/dev-skills/internal-comms)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/internal-comms"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/internal-comms.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.00077 | $0.00780 |
| Opus 5 | $0.00039 | $0.00390 |
| Sonnet 5 | $0.00015 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
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 6d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal Communications
Core Principle
Internal comms should be brief, informative, and actionable. No filler. No padding. Respect your reader's time.
Daily Standup (DSU) Format
Structure
Yesterday: [what you completed — be specific]
Today: [what you're working on]
Blockers: [anything blocking you — or "none"]
Taglish Style (for Filipino dev teams)
Good afternoon.
Yesterday, na-finish ko yung [task].
Today, mag-wo-work ako sa [task].
[Wala naman blocker. / May blocker ako — [describe].]
That's all from me, [Name].
Passing the floor
That's all from me, [next person's name].
Rules
- Be specific — "fixed the auth bug" not "did some coding"
- Name the story/ticket if relevant
- Blockers are for the team, not personal updates
- Keep it under 60 seconds when spoken
Sprint Update
## Sprint [X] Update — [Date]
**Status:** On track / At risk / Behind
**Completed this sprint:**
- [Story/task] — [brief outcome]
- [Story/task] — [brief outcome]
**In progress:**
- [Story/task] — [current status, ETA]
**Blockers:**
- [blocker] — [what you need to resolve it]
**Next sprint focus:**
- [preview of upcoming work]
Leadership / Stakeholder Update
Use BLUF (Bottom Line Up Front):
[One sentence: what they need to know]
[2-3 sentences: context and detail]
[Optional: what decision or action you need from them]
Example:
The Query Clarity Assessment Agent is code-complete and
pending final integration review.
Unit and integration test coverage is at 95%+.
The PR is on hold pending Anand's return to finalize
the Document Extraction dependency.
Expected deployment: end of next sprint.
Slack / Team Message Guidelines
- Lead with the point — don't bury the main message
- @mention only when action is needed from that person
- Use threads for follow-ups to keep channels clean
- Emoji reactions to acknowledge without cluttering threads
- Mark urgent clearly — "⚠️ Heads up:" or "🚨 Action needed:"
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.
- 6d ago First seen · 124 lines · 0 tokens per session scan A fdd0720f554b
internal-comms is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 780 once invoked, about $0.0004 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-31.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
markdown-compression
Safely compresses narrative Markdown using deterministic compaction plus validator checks. Only for allowlisted and gated artifacts.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-implement-qc-loop
Run implement and QC in a continuous loop. Direct command-bar dispatch only; do not select for general queries.