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 bostonaholic/team --skill principle-explicit-intentgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/principle-explicit-intent)<a href="https://agentmods.dev/skills/bostonaholic/team/principle-explicit-intent"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/principle-explicit-intent.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.00030 | $0.00213 |
| Opus 5 | $0.00015 | $0.00106 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
principle-explicit-intent 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.
What it actually says
Explicit Intent
Perform merges, pushes over published history, public closes, and deletions only on the user's stated intent, never inferred from state.
- Do not infer ship intent from green, rebase intent from behind, or abandon intent from stale.
- Require one yes per irreversible mutation; a named set authorizes that set, never unnamed items or adjacent change classes.
- Treat authorization as permission to finish the verified act, and nothing beyond it.
- Use granted authorization without re-asking; after gates pass, finish. Bound and report any confirmation churn.
- Put
"Invoke ONLY on … never infer …"in descriptions of skills whose invocation authorizes side effects; setdisable-model-invocationfor stricter host-enforced entry guards. - Put the guard at each in-run approval instead when invocation alone authorizes no mutation.
What ships with it
1 file 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.
- yesterday Changed · -20 lines · -17 tokens per session c904e08408f5
- 3d ago First seen · 37 lines · 47 tokens per session scan A 63802722dc4d
principle-explicit-intent is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 213 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.