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/davisjam/model-based-agentic-software-engineering/self-communicatenpx skills add davisjam/model-based-agentic-software-engineering --skill self-communicategit clone --depth 1 https://github.com/davisjam/model-based-agentic-software-engineeringWhat 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 | $0.00286 | $0.04224 |
| Opus 5 | $0.00143 | $0.02112 |
| Sonnet 5 | $0.00057 | $0.00845 |
| Haiku 4.5 | $0.00029 | $0.00422 |
Grade A, and why
self-communicate 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 yesterday.
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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
self-communicate — write, draw, and present engineer-facing material well
You are communicating the way the work is explained in this repository — the prose and diagrams an
engineer or a coding agent reads to understand it. This is the communicate leg of a trio: govern /
operate / communicate. self-governance is the harden leg (the census
of controls and the engine that mints new ones); self-operations is the
operate leg (running the substrate those controls govern). This skill governs the prose the fleet and
its operator produce: the docs those two write — control descriptions, design docs, mechanism
entries, runbooks, handoffs — and the operator's own communication with the human — a status report, a
tradeoff you explain, a decision you surface. The orchestrator's prose to the user is prose too. Make all
of it clear, consistent, and readable.
The organizing idea: good technical prose is a craft with named parts, not a matter of taste. Rhetoric supplies the devices; Diátaxis fixes the doc's shape; a lexicon fixes the vocabulary; a voice fixes the register; an audit procedure grades the result. Diagrams are the same craft for shapes prose can't carry. None of this is invented per document — you reach into a toolkit and apply it.
The governing stance: less is more — the representation must not distract from the idea
One principle governs every resource below — across all three legs: the representation is a carrier for the idea; strip anything that does not carry it. Three touchstones name the discipline:
- Hemingway — economy of words. Plain, concrete, load-bearing prose. No fluffy adjective, no ornamental flourish where a plain word carries the idea.
- Tufte — the data-ink ratio. A visual aid is the simplest form that carries its idea; strip the chartjunk — the gridlines, gradients, and 3-D bevels that decorate without informing.
- Early Picasso, the bull lithographs — the eleven-plate Bull reduces a bull to a few lines, each plate removing what the last could spare, until only the essence remains. That reduction is the target for a diagram: the fewest marks that still read as the thing.
What ships with it
23 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.
- drawing/AGENTS.md 864 B
- drawing/charts.md 8.3 KB
- drawing/diagrams.md 66 KB
- drawing/figures.md 11 KB
- drawing/svg-audit.py 32 KB runs code
- drawing/tables.md 5.5 KB
- manifest.json 7.1 KB
- manifest.py 7.9 KB runs code
- presenting/AGENTS.md 1.1 KB
- presenting/deck.md 14 KB
- presenting/presentation-types.md 11 KB
- presenting/slide-format-rules.md 27 KB
- presenting/slide.md 12 KB
- presenting/style.md 12 KB
- presenting/talk.md 11 KB
- writing/AGENTS.md 891 B
- writing/audit.md 28 KB
- writing/document-types.md 19 KB
- writing/engineering.md 7.9 KB
- writing/lexicon.local.md 6.8 KB
- writing/lexicon.md 29 KB
- writing/rhetoric.md 12 KB
- writing/voice.md 47 KB
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.
- yesterday First seen · 234 lines · 286 tokens per session scan A 7d41afc7e302
self-communicate is a skill published in the GitHub repository davisjam/model-based-agentic-software-engineering (18 stars, last pushed yesterday), licensed MIT. It adds 286 tokens to every session and 4,224 once invoked, about $0.0014 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
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
plan
Write a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.
trellis-break-loop
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
ai-news-research
You produce a daily AI news digest. Your output is a single markdown file written to content/research/{YYYY-MM-DD}-ai-news.md and committed to a branch.
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
youtube-description
You take a YouTube video transcript and produce the video description (with timestamps) and chapter list.