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 commands/kossakovsky/cc-plugins/submitgit clone --depth 1 https://github.com/kossakovsky/cc-pluginsWhat 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.00012 | $0.01326 |
| Opus 5 | $0.00006 | $0.00663 |
| Sonnet 5 | $0.00002 | $0.00265 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
submit 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 yesterday.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Plugin to Marketplace
Guide the user through submitting their plugin to the community marketplace (kossakovsky/cc-plugins).
Arguments
$1(optional): Path to the plugin directory. If not provided, detect from current directory.
Instructions
Step 1: Locate the Plugin
- If
$1is provided, use that path - Otherwise, look for
.claude-plugin/plugin.jsonin the current directory or parent directories - If not found, ask the user which plugin to submit
Read the plugin's .claude-plugin/plugin.json and README.md.
Step 2: Validate the Plugin
Run the same checks as /plugin-development:validate:
.claude-plugin/plugin.jsonexists and is valid JSON- Required fields present:
name(kebab-case),version,description README.mdexists with installation and usage sections- At least one component directory (commands/, skills/, agents/, or hooks/)
- No security issues (no hardcoded secrets, no data exfiltration patterns)
If validation fails, show errors and stop. The user must fix issues before submitting.
Step 3: Generate Marketplace Entry
Using data from plugin.json, generate a marketplace entry:
{
"name": "<from plugin.json>",
"description": "<from plugin.json>",
"version": "<from plugin.json>",
"source": "./plugins/<name>",
"author": { "name": "<from plugin.json or ask user>" },
"category": "<ask user to choose>",
"tags": ["<from plugin.json keywords or ask user>"],
"keywords": ["<from plugin.json keywords or ask user>"]
}
Available categories: utilities, developer-tools, productivity, ai-tools, integrations.
Show the generated entry to the user for confirmation.
Step 4: Check Prerequisites
Check if gh CLI is available:
gh --version
If gh is available: Offer automated submission (Step 5a).
If gh is not available: Provide manual instructions (Step 5b).
Step 5a: Automated Submission (with gh CLI)
Ask the user for confirmation before each step.
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.
- yesterday First seen · 183 lines · 12 tokens per session scan A 5636eb8667ae
submit is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 1,326 once invoked, about $0.0001 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.