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/rabithua/feedbackserverplugin/publish-roadmap-releasesnpx skills add Rabithua/FeedbackServerPlugin --skill publish-roadmap-releasesgit clone --depth 1 https://github.com/Rabithua/FeedbackServerPluginWrote 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/rabithua/feedbackserverplugin/publish-roadmap-releases)<a href="https://agentmods.dev/skills/rabithua/feedbackserverplugin/publish-roadmap-releases"><img src="https://agentmods.dev/badge/skills/rabithua/feedbackserverplugin/publish-roadmap-releases.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.00069 | $0.00508 |
| Opus 5 | $0.00034 | $0.00254 |
| Sonnet 5 | $0.00014 | $0.00102 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
publish-roadmap-releases 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 today.
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
Publish FeedbackServer 2.0 roadmaps and Releases
Resolve the Product and exact Developer Post, Item, Release, translation, or App Store binding with the matching list/get tool. Never guess IDs. Draft inspection and preview are read-only; a request to review, draft, plan, or preview does not authorize publication or another write.
Developer Posts are independent Activity content and do not accept votes or replies. Roadmap state
belongs to each Product placement and uses urgent, later, or undecided, plus rank, visibility,
and archived state. Release translations contain localized body text; the Release version is the
heading. Resolve the linked Items before publishing because publication archives those Items from the
roadmap.
Use list_developer_posts/get_developer_post, list_items/get_item, and
list_releases/get_release for exact selection. Draft creation uses the corresponding create tool.
Edits, placement changes, publication state, and deletions use the corresponding update, publication,
translation, or delete tool and follow the risk marker the server advertises. create_release and
update_release are protected because they may publish or archive linked Items.
For App Store import, read or configure the Product's binding with an explicit numeric App Store ID,
two-letter storefront, and BCP-47 locale. Never infer locale from storefront. Use
preview_latest_app_store_release for inspection. import_latest_app_store_release creates a draft
or adds a missing translation and does not overwrite an existing translation.
For a publication, public edit, placement change, protected translation, import, or deletion, prefer
native MCP elicitation. If the client cannot elicit and the tool returns confirmation_required,
show the exact target, text, locale, Item-archive effect, and public availability change; wait for
explicit approval; then repeat the same operation with identical arguments plus confirm: true.
Never use a confirmation identifier. If current state differs from the reviewed state, reread it and
obtain fresh approval. Never retry a mutation automatically.
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.
- today Changed · +10 lines · +2 tokens per session 2cae862b1fbc
- 4d ago First seen · 25 lines · 67 tokens per session scan A 202f398c4836
publish-roadmap-releases is a skill published in the GitHub repository Rabithua/FeedbackServerPlugin (0 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 508 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-31.
Other skills, from other repositories
trulens-evaluation-setup
Configure feedback functions and selectors for TruLens evaluations.
honesty-communication
当用户问怎么真诚沟通/拒绝别人/给反馈/不想说场面话、或发现自己在隐瞒时调用。 核心理念: 撒谎会先骗到自己(费曼: 你最容易愚弄的人是你); 彻底诚实=所想与所说一致; 具体表扬、一般批评; 秘密越少快乐越多。 不适用于: 需要外交辞令的谈判策略(可以诚实但不必全说)。 Triggers: 诚实/沟通/拒绝/批评/表扬/秘密/场面话/honesty/communication/feedback.
human-review
Open an HTML file, Markdown file, or localhost page in the browser so the user can edit text directly and leave comments on specific parts, then send all edits and comments back to you. Use after writing or updating something the user will read — specs, plans, reports, newsletter drafts, landing pages, slide decks…
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
Code Review Excellence
Master code review best practices with constructive feedback patterns, quality assurance standards, review checklists, security considerations, and collaborative improvement techniques for high-quality software delivery.
code-review-quality
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.