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.
git clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/commands/jnpiyush/agentx/cowork-plugin-create)<a href="https://agentmods.dev/commands/jnpiyush/agentx/cowork-plugin-create"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/cowork-plugin-create/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/commands/jnpiyush/agentx/cowork-plugin-create"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/cowork-plugin-create.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.00038 | $0.01030 |
| Opus 5.5 | $0.00015 | $0.00412 |
| Sonnet 5.5 | $0.00008 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
Create Cowork Plugin Package 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Cowork Plugin Package
Inputs
{{name}}: Cowork plugin name{{capability}}: Business capability the plugin supports{{skills}}: Specialized skills to bundle, ornonefor a connector-only package{{connector}}: MCP connector requirement, ornone{{outputDir}}: Package output directory
Requirements
- Read
.github/skills/development/cowork-plugin-creator/SKILL.mdin full before authoring files. - Decompose
{{capability}}into non-overlapping skills. Each skill owns one stage, task, or domain and defers explicitly at its boundaries. The package must declare at least one skill or at least one connector. - Create
{{outputDir}}/<plugin-name>/manifest.jsonwithmanifestVersion, a stable GUIDid,version,developer,name,description,icons,agentSkills, and anyagentConnectors. Do not add fields outside the supported schema. - Add
color.pngat 192x192 pixels andoutline.pngat 32x32 pixels, and reference both fromicons. - Create
skills/<skill-name>/SKILL.mdfor every skill. The frontmatternamemust be kebab-case and match its folder name exactly, and the description must contain realistic trigger phrases. - Register every skill folder in
agentSkills. Populatereferences/andscripts/inside a skill folder only when that skill needs them. - When
{{connector}}is notnone, add anagentConnectorsentry with an HTTPSmcpServerUrl, a packagedmcpToolDescriptionfile undertools/, and anauthorizationblock whosetypeisNone,OAuthPluginVault,ApiKeyPluginVault, orDynamicClientRegistration. Every type exceptNonerequires a vaultreferenceId. Never embed credentials in the package. - Do not leave TODO markers, generic placeholders, secrets, personal data, customer-sensitive data, or unsupported claims.
- Require human review before sending, publishing, deleting, approving, or taking another consequential action.
- Run
.github/skills/development/cowork-plugin-creator/scripts/New-CoworkPluginPackage.ps1against the completed source directory. - Verify the zip contains
manifest.json, both icons, and every registered skill folder at the archive root with no wrapper directory. - Return the generated zip path and a concise list of packaged files. The final deliverable must be the zip file, not only a Markdown response or source directory.
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.
- 7d ago Changed 6714986b13e1
- 1mo ago Changed 7d33a46084e6
- 1mo ago First seen · 90 lines · 38 tokens per session scan A e4875806b3bc
Create Cowork Plugin Package is a command published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,030 once invoked, about $0.0002 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-09-06.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.