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 ShipToday/forge-plugin-codex --skill forge-feedbackgit clone --depth 1 https://github.com/ShipToday/forge-plugin-codexWrote 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/shiptoday/forge-plugin-codex/forge-feedback)<a href="https://agentmods.dev/skills/shiptoday/forge-plugin-codex/forge-feedback"><img src="https://agentmods.dev/badge/skills/shiptoday/forge-plugin-codex/forge-feedback/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/shiptoday/forge-plugin-codex/forge-feedback"><img src="https://agentmods.dev/badge/skills/shiptoday/forge-plugin-codex/forge-feedback.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.00160 | $0.01477 |
| Opus 5.5 | $0.00064 | $0.00591 |
| Sonnet 5.5 | $0.00032 | $0.00295 |
| Haiku 4.5 | $0.00016 | $0.00148 |
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 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 — 147 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.
Question delivery
Codex question lifetime
For fixed choices, prefer supported, permitted native UI. Forge may use a
negotiated MCP form; after an answered RE-ENTRY, never ask the question again.
Otherwise use request_user_input or request_user_input_async only when
callable and permitted for this question's purpose in the current mode.
Assess MCP forms and each host tool independently. In Default mode, a
Plan-only blocking tool does not prohibit the async tool: check its own
permissions before numbered text. An unexplained MCP rejection is not a
policy-wide denial. Explicit policy prohibiting the question across routes
still applies.
Prefer a compatible blocking control. A permitted async picker may be used
once; its string options carry exact labels, so show descriptions and full
approval material in prose before opening it. Respect each tool's actual
schema: blocking input accepts 2–3 options; that limit does not apply to every
native control. Do not remove choices to make them fit.
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 Changed · +5 lines 9bd9859968fb
- 23d ago Changed · +34 lines 78917bc50e27
- 1mo ago Changed · +1 lines a2ff987fe271
- 2mo 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,477 once invoked, about $0.0006 per session on Opus 5.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
mindtrain
Configure a private MindTrain instance, query its knowledge catalog, create user-approved training domains and knowledge points from AI dialogue or local reference libraries, and run persistent conversational training through Trainer MCP. Use when the user configures MindTrain, asks what domains or topics exist…
image-context-runtime
Use for image-heavy Codex work when generated or inspected media should stay behind a bounded MCP boundary and the controlling task should receive only durable Job IDs, hashes, relative references, and compact text handoffs.
registry-broker-orchestrator
Use Registry Broker to discover and summon specialist agents for focused subtasks from inside Codex.
xrocket-exchange
Use the unofficial xRocket Exchange MCP to inspect spot markets and accounts, trade autonomously inside an operator-configured daily value limit, or prepare explicitly approved transfers and withdrawals. Trigger when a request concerns xRocket markets, account data, deposits, trading, transfers, withdrawals, or its…
use-wsl
Use one wslexec call per user-requested non-interactive Linux execution when Windows-native Codex needs WSL. Preserve the project working directory and never probe or retry automatically.
proton-drive-cli
Use when the user wants to browse, upload, download, organize, share, or authenticate Proton Drive through the Proton Drive CLI MCP server and official Proton Drive CLI.