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-workflowgit 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-workflow)<a href="https://agentmods.dev/skills/shiptoday/forge-plugin-codex/forge-workflow"><img src="https://agentmods.dev/badge/skills/shiptoday/forge-plugin-codex/forge-workflow/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-workflow"><img src="https://agentmods.dev/badge/skills/shiptoday/forge-plugin-codex/forge-workflow.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.00203 | $0.13882 |
| Opus 5.5 | $0.00081 | $0.05553 |
| Sonnet 5.5 | $0.00041 | $0.02776 |
| Haiku 4.5 | $0.00020 | $0.01388 |
Grade A, and why
forge-workflow 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 9d 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 — 1,184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Workflow
You are helping an organization admin manage custom Forge workflows conversationally — either authoring a new workflow or deleting an existing org- or team-scoped override. You do this conversationally, not as a step-by-step wizard.
Forge is an MCP server; the tools you will call are:
forge__list_skills_catalog— returns the skills, workflows, and the field schema manifest the server considers admin-editable. Workflow rows here have only{id, name, description, scope}— step lists are NOT included.forge__get_workflow— returns a single workflow's full definition (preset + ordered steps with skill metadata). Use this to retrieve the baseline before drafting an override.forge__save_workflow— atomically writes a new workflow (and any new custom skills) to the Forge catalog.forge__delete_workflow— removes an org- or team-scoped preset, so the scope falls back through the cascade (org → system, team → org → system). Note that Forge's built-in workflows ship disabled, so falling back to the system default also stops the workflow running — see the Delete path for how to state this to the admin.
Why this skill is schema-driven
You do not carry a hardcoded list of workflow / step fields. The
catalog response includes a field_schema block that enumerates every
admin-editable field on the workflow preset and its steps. When the
server adds a new column, the manifest grows, and this skill picks it
up automatically — there is no list of fields in this prompt to keep
in sync.
Rule: All field names, types, defaults, examples, and validators come from
field_schemain the catalog response. Never invent field names, never hardcode the editable set, and never assume a field is nullable / required without checking its manifest entry.
How to ask the admin
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.
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.
- 9d ago Changed · +32 lines 98459b755fb6
- 16d ago Changed · +13 lines aa8d0e5915a9
- 19d ago Changed · +114 lines 8dc5e6de7406
- 21d ago Changed · +40 lines 8a67fc4b6394
- 25d ago Changed · +97 lines a72673c9ab05
- 1mo ago Changed · +5 lines 61f8572bfb4a
- 1mo ago First seen · 883 lines · 203 tokens per session scan A 97bc703a7554
forge-workflow is a skill published in the GitHub repository ShipToday/forge-plugin-codex (2 stars, last pushed 10d ago), licensed MIT. It adds 203 tokens to every session and 13,882 once invoked, about $0.0008 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
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
continue-project
Find the user's saved Glif project, show its media, and add new work to it without starting a separate project. Use when: "show my recent Glif projects", "open my last image", "keep going on that one", "make 5 variations to A/B test", "same but vertical", "make a version for TikTok", "resize it to every format", "same…
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks.