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/data-wise/craft/distribution-strategistnpx skills add Data-Wise/craft --skill distribution-strategistgit clone --depth 1 https://github.com/Data-Wise/craftWrote 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/data-wise/craft/distribution-strategist)<a href="https://agentmods.dev/skills/data-wise/craft/distribution-strategist"><img src="https://agentmods.dev/badge/skills/data-wise/craft/distribution-strategist.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 | $0.00063 | $0.01251 |
| Opus 5 | $0.00032 | $0.00626 |
| Sonnet 5 | $0.00013 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
distribution-strategist scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **Surface note:** a distribution *channel* (Homebrew / PyPI / npm / curl) is How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribution Strategist
Expert in selecting and prioritizing distribution channels for software projects.
Surface note: a distribution channel (Homebrew / PyPI / npm / curl) is orthogonal to a Claude surface (Code CLI · Desktop DXT/MCPB · Cowork). A plugin may ship via Homebrew yet still need a separate DXT artifact to reach Desktop. For the surface model see
dist-extrasandcommands/dist/surfaces.md.
Role
Analyze project characteristics and recommend the most effective distribution strategy, considering:
- Project type (CLI, library, app, service)
- Target audience (developers, end-users, enterprises)
- Platform requirements (cross-platform, OS-specific)
- Maintenance burden vs reach tradeoffs
Distribution Channel Matrix
By Project Type
| Project Type | Primary Channels | Secondary Channels |
|---|---|---|
| CLI Tool | Homebrew, curl script | npm/pip/cargo, GitHub releases |
| Library | Package manager (npm/pip/cargo) | GitHub packages |
| Desktop App | Homebrew cask, DMG/MSI | App stores |
| Web Service | Docker Hub | Helm charts, cloud marketplaces |
By Language
| Language | Package Manager | Binary Distribution |
|---|---|---|
| Python | PyPI, pip | pipx, Homebrew |
| JavaScript | npm, yarn | npx |
| Rust | crates.io, cargo | Homebrew, curl |
| Go | go install | Homebrew, curl |
| Ruby | RubyGems | Homebrew |
By Audience
| Audience | Preferred Channels | Why |
|---|---|---|
| Developers | Package managers, GitHub | Familiar workflow |
| DevOps | Docker, Homebrew, curl | Automation-friendly |
| End Users | App stores, installers | GUI, auto-updates |
| Enterprise | Private registries, air-gapped | Security, compliance |
Strategy Template
## Distribution Strategy for [Project]
### Project Analysis
- **Type**: CLI tool / Library / Application
- **Language**: Python / Node / Go / Rust
- **Platforms**: macOS / Linux / Windows
- **Audience**: Developers / DevOps / End Users
### Recommended Channels (Priority Order)
#### Tier 1: Essential (Launch)
1. **[Primary Channel]**
- Reach: High
- Effort: Low
- Why: [Reason]
2. **GitHub Releases**
- Reach: Medium
- Effort: Low
- Why: Always available, works everywhere
#### Tier 2: Growth (Post-Launch)
3. **[Secondary Channel]**
- Reach: Medium
- Effort: Medium
- Why: [Reason]
#### Tier 3: Expansion (Mature)
4. **[Additional Channels]**
- Consider based on user feedback
### Implementation Order
1. [ ] Set up primary channel
2. [ ] Configure GitHub releases
3. [ ] Add installation docs to README
4. [ ] Create install script for curl users
5. [ ] Expand to secondary channels
### Maintenance Considerations
- Update frequency: [Release cycle]
- Automation: [CI/CD for publishing]
- Versioning: [Semver strategy]
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.
- 4d ago First seen · 197 lines · 63 tokens per session scan A ea425090eb93
distribution-strategist is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,251 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
explore
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment. Generates ASCII visualizations, import graphs, and design pattern detection with cross-session memory storage. Use when exploring a repo, discovering architecture, onboarding to a…
audit-full
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing. Loads entire codebases for cross-file pattern detection and generates structured audit reports with severity-ranked findings. Use when you need whole-project analysis…
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do…
architecture-status
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants…
pragmatic-guard
Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.