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 Brainrot-Creations/claude-plugins --skill contribute-workflowgit clone --depth 1 https://github.com/Brainrot-Creations/claude-pluginsWrote 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/brainrot-creations/claude-plugins/contribute-workflow)<a href="https://agentmods.dev/skills/brainrot-creations/claude-plugins/contribute-workflow"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/contribute-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/brainrot-creations/claude-plugins/contribute-workflow"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/contribute-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.00032 | $0.00368 |
| Opus 5.5 | $0.00013 | $0.00147 |
| Sonnet 5.5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
contribute-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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- contribute-workflow — 100% identical, 0 lines differ
What it actually says
After successfully completing a multi-step goal through your own discovery, contribute the full procedure:
-
Choose a
workflow_key— snake_case slug describing the procedure:- Good:
send_connection_with_note,post_linkedin_article,submit_github_issue - Bad:
do_the_thing,linkedin_stuff
- Good:
-
Write a clear
descriptionof what the workflow accomplishes:- Good: "Send a LinkedIn connection request with a personalized note"
- Bad: "Connect with someone"
-
Build the
stepsarray in execution order. For each step:action_name— snake_case name for this action (e.g.click_add_note_in_modal)method.type— "css", "xpath", "aria", or "visual"method.value— the exact selector or visual description that workedmethod.context— optional: where on the page this selector appliesnotes— optional: anything that would help another agent (e.g. "Wait for modal to open before this step")
-
Call
hive_contribute_workflow(domain, workflow_key, description, steps).
What makes a good workflow contribution
- Every step is reproducible — not dependent on specific account state or session data
- Step names are descriptive enough that another agent can understand the sequence
- Steps include context hints when a selector only works in a specific page state
- You've verified the full sequence works end-to-end before contributing
The collective builds on what you contribute. Good contributions compound.
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.
- 2mo ago First seen · 33 lines · 32 tokens per session scan A e6ace4a5504f
contribute-workflow is a skill published in the GitHub repository Brainrot-Creations/claude-plugins (23 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 368 once invoked, about $0.0001 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-30.
contribute-workflow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| contribute-workflowBrainrot-Creations/claude-plugins | Skill | 23 | 4mo ago | MIT | A | 32 | Claude Code |
| monday-planninggtapps/hermitd | Skill | 84 | yesterday | MIT | A | 18 | Claude Code |
| design-system-referencewigtn/wigtn-plugins | Skill | 45 | 8d ago | Apache-2.0 | A | 43 | Claude Code |
| vigil-instrumenttonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 61 | Claude Code |
| boss-briefingsehoon787/my-claude | Skill | 16 | 2d ago | MIT | A | 23 | Claude Code |
| monitor-activategtapps/hermitd | Skill | 84 | yesterday | MIT | A | 12 | Claude Code |
| eurodnskochetkov-ma/claude-brewcode | Skill | 39 | yesterday | MIT | A | 31 | Codex |