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 conorbronsdon/agent-context-os --skill press-outreachgit clone --depth 1 https://github.com/conorbronsdon/agent-context-osWrote 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/conorbronsdon/agent-context-os/press-outreach)<a href="https://agentmods.dev/skills/conorbronsdon/agent-context-os/press-outreach"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-context-os/press-outreach/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/conorbronsdon/agent-context-os/press-outreach"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-context-os/press-outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 14 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00060 | $0.00619 |
| Opus 5 | $0.00030 | $0.00309 |
| Sonnet 5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
press-outreach 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 9d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Press Outreach — Musician
Draft a pitch email to a blog, playlist curator, or press contact. Load artist context and promotion strategy before writing.
Before writing
- Read
projects/example-musician/artist-context.md— catalog, sound, audience, any existing press - Read
projects/example-musician/promotion-strategy.md— what's being pitched, current release, target outlets - Read
writing/skills/avoid-ai-writing/SKILL.md— apply its writing audit - Ask (or check the conversation) for: the specific outlet/contact, what you're pitching (release, tour, story), and any context about why this contact is a fit
Email types
Blog / editorial pitch
- Goal: get a review, feature, or premiere
- Angle: what's the story? A new sound, a personal narrative, a regional spotlight, a tie-in to a larger trend?
- Length: short. 3-4 paragraphs max. They get hundreds of these.
Playlist curator pitch
- Goal: get on a specific playlist
- Angle: why does this track fit their playlist? Be specific — name a song already on it, describe the mood match
- Length: even shorter. 2-3 sentences + the link.
Radio / podcast pitch
- Goal: airplay, interview, or feature
- Angle: what makes this artist worth their audience's time?
- Length: medium — enough to show you've done your homework, short enough to respect theirs
Writing rules
- Personalize the opener — reference something specific about the outlet (a recent piece, a playlist they curated, an artist they covered)
- Get to the point in the first sentence — don't bury the ask
- Include: what you're pitching, why it fits their audience, one strong line about the music, and the links
- No AI-isms — no "I hope this email finds you well," "I am reaching out because," "I would be honored"
- Don't oversell — "I think your readers will love this" is cringe. Describe the music and let them decide.
- Include a clear call to action: "Happy to send a download link" or "Would love to be considered for [playlist]"
Output format
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.
- 9d ago First seen · 50 lines · 60 tokens per session scan A 6feec6197e00
press-outreach is a skill published in the GitHub repository conorbronsdon/agent-context-os (23 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 619 once invoked, about $0.0003 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
deep-dive
2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection.
growth-distribution
Cross-platform content distribution and growth strategy for DYA app across 10+ platforms (Xiaohongshu, Douyin, TikTok, Instagram Reels, X/Twitter, Reddit, Weibo, Bilibili, WeChat Video). Use when planning social media posts, distributing video content, optimizing for platform algorithms, writing platform-specific…
agent-protocol
Specification for making MUSE role files machine-readable as an Agent Protocol — enabling multi-agent coordination and tool interoperability.
coordinator-mode
Multi-agent coordination SOP derived from Anthropic's internal coordinator architecture. Use when orchestrating parallel workers, dispatching subagents, planning multi-step implementations, or when tasks require research→synthesis→implementation→verification workflow. Triggers: 'coordinate', 'dispatch workers'…
creating-skills
Guide for creating Claude Code skills following Anthropic's official best practices. Use when user wants to create a new skill, build a skill, write SKILL.md, or needs skill creation guidelines. Provides structure, naming conventions, description writing, and quality checklist.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…