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/shiptoday/forge-plugin-codex/forge-feedbacknpx skills add ShipToday/forge-plugin-codex --skill forge-feedbackgit clone --depth 1 https://github.com/ShipToday/forge-plugin-codexWhat 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.00160 | $0.01024 |
| Opus 5 | $0.00080 | $0.00512 |
| Sonnet 5 | $0.00032 | $0.00205 |
| Haiku 4.5 | $0.00016 | $0.00102 |
Grade A, and why
forge-feedback 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Feedback
You are helping the user send feedback to the ShipToday team from inside
their AI coding session. Delivery goes through Forge's shared, MCP-owned
feedback backend via the forge__send_feedback tool — you only deliver
through that tool, never through any other tool, and you never send anything
until the user has seen the exact payload and explicitly confirmed.
Privacy contract (non-negotiable):
- No feedback content is persisted to any database. It reaches the ShipToday team and nothing else.
- Do not disclose the delivery mechanism to the user. Don't name the channel or transport the feedback is sent through — just confirm it reaches the ShipToday team. How and where it is delivered is an internal detail.
- Session context must be sanitized before it leaves the session. You are responsible for the first scrub; the backend re-sanitizes defensively, but do not rely on that.
- Nothing is sent without explicit confirmation. If the user declines, send
nothing, make no
forge__send_feedbackcall, and exit gracefully.
Step 1 — Collect the feedback
Ask the user what feedback they'd like to share with the ShipToday team. Keep it to one open question; let them write freely. If they already stated their feedback when invoking the skill, use that and skip re-asking.
Step 2 — Gather and sanitize session context
Optionally enrich the submission with brief, relevant context from the current session that would help ShipToday act on the feedback — e.g. what the user was doing, which Forge workflow/step was active, the tool or command involved, and any error message. Keep it short (a few lines).
Sanitize the context before showing or sending it. Remove:
- Secrets and credentials: API keys, tokens, bearer tokens, JWTs, passwords,
KEY=valueenv assignments, connection strings. - Private customer data and PII: emails, names, customer identifiers, file contents that aren't relevant to the feedback.
- Anything the user wouldn't want shared outside their org.
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.
- 2d ago First seen · 107 lines · 160 tokens per session scan A d5ddbb00b9b9
forge-feedback is a skill published in the GitHub repository ShipToday/forge-plugin-codex (2 stars, last pushed 3d ago), licensed MIT. It adds 160 tokens to every session and 1,024 once invoked, about $0.0008 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
minecraft-modpack-server
Host modded Minecraft servers (CurseForge, Modrinth).
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
infra-audit
Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
design
Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and documents the design language. In new projects, asks a few questions and generates a starter manifest. The post-edit hook reads the manifest and flags deviations.