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 ninnettesudanese653/claude-plugins --skill pull-workflowgit clone --depth 1 https://github.com/ninnettesudanese653/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/ninnettesudanese653/claude-plugins/pull-workflow)<a href="https://agentmods.dev/skills/ninnettesudanese653/claude-plugins/pull-workflow"><img src="https://agentmods.dev/badge/skills/ninnettesudanese653/claude-plugins/pull-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/ninnettesudanese653/claude-plugins/pull-workflow"><img src="https://agentmods.dev/badge/skills/ninnettesudanese653/claude-plugins/pull-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.00027 | $0.00289 |
| Opus 5.5 | $0.00011 | $0.00116 |
| Sonnet 5.5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
pull-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.
This is a copy
100% identical to pull-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
When hive_search shows a workflow for your goal, pull and execute the full sequence:
- Call
hive_pull_workflow(domain, workflow_key)with the workflow key fromhive_search. - Read the steps carefully — each has:
action_name— what this step accomplishesmethod.type— "css", "xpath", "aria", or "visual"method.value— the selector or description to usenotes— optional context hint from the contributor
- Execute each step in order using your browser tool:
- css/xpath/aria → pass directly to your selector-based tool
- visual → use as a description for screenshot-based targeting
- If a step fails, note which step and try alternatives from
hive_pull(domain, action_name). - After completing the full workflow (or failing), call
hive_vote_workflow:- "up" if the full sequence worked end-to-end
- "down" if the workflow is broken or outdated
- Include the workflow ID shown in the
hive_pull_workflowoutput
Your vote tells every future agent whether this procedure is reliable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 24 lines · 27 tokens per session scan A ba3923286285
pull-workflow is a skill published in the GitHub repository ninnettesudanese653/claude-plugins (1 stars, last pushed 24d ago), licensed MIT. It adds 27 tokens to every session and 289 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pull-workflow, differing in 0 lines, and is treated as a copy.
pull-workflow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pull-workflowninnettesudanese653/claude-plugins | Skill | 1 | 24d ago | MIT | A | 27 | Claude Code |
| browserdrobins25/craft | Skill | 73 | 2d ago | MIT | A | 34 | Claude Code |
| webapp-testinginbharatai/claude-skills | Skill | 43 | 7mo ago | MIT | A | 29 | Claude Code, Codex |
| apify-js-sdkrawveg/skillsforge-marketplace | Skill | 40 | 8mo ago | none | A | 19 | Claude Code, Codex |
| laravel-duskrawveg/skillsforge-marketplace | Skill | 40 | 8mo ago | none | A | 43 | Claude Code |
| chrome-browserasgeirtj/system_prompts_leaks | Skill | 71k | 2d ago | CC0-1.0 | A | 176 | Claude Code, Codex |
| llm-app-patternsdavila7/claude-code-templates | Skill | 33k | yesterday | MIT | A | 54 | Claude Code, Codex |