Borrowing it
Nothing to install: this file belongs to ertra/pm-brain-for-cursor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ertra/pm-brain-for-cursor/main/.cursor/skills/create-internal-feature-announcement/SKILL.mdgit clone --depth 1 https://github.com/ertra/pm-brain-for-cursorWrote 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/ertra/pm-brain-for-cursor/create-internal-feature-announcement)<a href="https://agentmods.dev/skills/ertra/pm-brain-for-cursor/create-internal-feature-announcement"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/create-internal-feature-announcement/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/ertra/pm-brain-for-cursor/create-internal-feature-announcement"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/create-internal-feature-announcement.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.02042 |
| Opus 5 | $0.00036 | $0.01021 |
| Sonnet 5 | $0.00014 | $0.00408 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
create-internal-feature-announcement 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 10d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal feature announcement (IFA) writer (pm-brain)
Produce 04-internal-feature-announcement.md by filling the IFA template from the PRD pack (01-–03-) and any extra sources the user names. Content is internal only; do not copy confidential customer identifiers into examples unless the user explicitly allows it.
Repo convention: Feature hub paths, skipping steps, and the skills table — see 02-templates/README.md (Feature hub convention, Skipping steps, Cursor skills).
This skill assumes a PRD pack exists; if 02-product-requirements.md and 03-success-metrics.md are missing, tell the user to run create-prd first or provide equivalent source paths.
Step 0: Locate the feature hub
- Ask for the PROJECT Jira key (
PROJECT-abcde) or the path to an existing feature hub folder. - Resolve the feature-hub folder:
projects/{PROJECT-KEY}-{slug}/.- If only the key is given, list
projects/and match thePROJECT-{KEY}-*directory. - If multiple match, show them and ask which one.
- If only the key is given, list
- Confirm the PRD pack exists in that folder:
01-product-brief.md,02-product-requirements.md, and03-success-metrics.md. If any are missing, tell the user to runcreate-prdfirst or provide explicit paths to equivalent docs.
Output
Save the deliverable to:
projects/{PROJECT-KEY}-{slug}/04-internal-feature-announcement.md
If the file already exists, ask whether to overwrite, create a dated backup, or choose a different name.
When to use this skill
- Aligning internal comms before or after launch
- Preparing Slack
#internal-feature-announcementcopy and internal FAQ stems - Handing off facts to support via the IFA before a customer-facing article
What you'll need
Critical inputs (collect in Step 1 if missing):
- Feature hub with
01-product-brief.md,02-product-requirements.md,03-success-metrics.md - Roadmap / release — Alpha, private beta, GA (or explicit TBD)
- Key contacts — PM, EM, PMM (names or
[PLACEHOLDER])
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.
- 10d ago First seen · 163 lines · 71 tokens per session scan A 3fdb7fa3df11
create-internal-feature-announcement is a skill published in the GitHub repository ertra/pm-brain-for-cursor (22 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 2,042 once invoked, about $0.0004 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
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.
mockup-device-3d
Static iPhone and MacBook 3D-style showcase with real HTML embedded on screens, glass-lens refraction, and 360-degree turntable composition.