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 JasonColapietro/suede-creator-skills --skill suede-newsroomgit clone --depth 1 https://github.com/JasonColapietro/suede-creator-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/jasoncolapietro/suede-creator-skills/suede-newsroom)<a href="https://agentmods.dev/skills/jasoncolapietro/suede-creator-skills/suede-newsroom"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-newsroom/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/jasoncolapietro/suede-creator-skills/suede-newsroom"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-newsroom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00194 | $0.03364 |
| Opus 5 | $0.00097 | $0.01682 |
| Sonnet 5 | $0.00039 | $0.00673 |
| Haiku 4.5 | $0.00019 | $0.00336 |
Grade A, and why
suede-newsroom 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 12d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suede Newsroom
Six chatbots pointed at the same brand are not a content team. A newsroom is the loop that connects them, and every arrow in it is a handoff with a contract:
idea -> research -> angle -> flagship -> distribution -> review -> performance -> playbooks
Break one arrow and the failure is predictable, not mysterious:
| Broken arrow | What ships instead |
|---|---|
| research never reaches the strategist | a generic angle any competitor could have written |
| the writer never sees the evidence packet | claims that drift one step past what the source says |
| distribution starts from the finished draft | five surfaces carrying the same shortened article |
| performance never reaches the playbooks | the same mistake repeated at a higher cadence |
This skill owns the pipeline: who decides what, what travels between them, and
how one idea becomes several assets that argue different things. Read
.agents/product-marketing.md first if it exists — it holds product, audience,
positioning, and proof, and nothing here restates it.
Founder-led mode. When the recurring source is a founder interview, voice note, or operator debrief, or when personal and company accounts need different jobs, read references/founder-content-loop.md before Step 1. It adds an intake contract and account lanes to this pipeline; the six role contracts, evidence gates, collision checks, approval boundary, and Keep/Test/Stop thresholds below remain unchanged.
Step 1 — Put the campaign in a file, not a conversation
One record per campaign at .agents/newsroom/<slug>.md. It is the only thing
that has to survive between roles, sessions, and restarts.
A conversation between roles has two failure modes a file does not: context dies on restart, and the next role has to infer which sentences were load-bearing. The record gives each role a predictable input and lets a human audit a campaign without reopening six sessions.
Keep it narrow — decisions and the evidence behind them. Drafts live beside it, not in it. The template and per-stage completion rules are in references/campaign-record.md.
What ships with it
7 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.
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.
- 12d ago First seen · 288 lines · 194 tokens per session scan A 9b3d5c98351d
suede-newsroom is a skill published in the GitHub repository JasonColapietro/suede-creator-skills (135 stars, last pushed today), licensed MIT. It adds 194 tokens to every session and 3,364 once invoked, about $0.0010 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
skill-router
Use when a [skill-router] route card appears in the turn, when no card appeared on a non-trivial task, or when a route looks wrong. Routes every prompt to the right installed skill, pairs it with a process skill, tiers enforcement, and briefs sub-agents. 79 local skills + plugin skills indexed.
generate-report
Generate a comprehensive summary report of the latest experiment including metrics, plots, and comparison with baseline. Use this after training and evaluation to create a shareable experiment summary.
evaluate-model
Load the latest model checkpoint, run evaluation on the test set, and generate a metrics report with confusion matrix. Use this after training to assess model performance or to re-evaluate a specific checkpoint.
run-pipeline
Run the full data science pipeline: validate raw data, preprocess, engineer features, train model, and evaluate. Use this when you want to execute the end-to-end ML pipeline or re-run it after data or code changes.
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
run-simulator
Build and launch the app in the iOS Simulator. Automatically selects an appropriate simulator device, boots it if needed, and installs and launches the app.