Borrowing it
Nothing to install: this file belongs to zuarbase/Zuar-Portal-MCP-Public. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zuarbase/Zuar-Portal-MCP-Public/main/.claude/commands/portal-bulk.mdgit clone --depth 1 https://github.com/zuarbase/Zuar-Portal-MCP-PublicWrote 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/zuarbase/zuar-portal-mcp-public/portal-bulk)<a href="https://agentmods.dev/commands/zuarbase/zuar-portal-mcp-public/portal-bulk"><img src="https://agentmods.dev/badge/commands/zuarbase/zuar-portal-mcp-public/portal-bulk/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/zuarbase/zuar-portal-mcp-public/portal-bulk"><img src="https://agentmods.dev/badge/commands/zuarbase/zuar-portal-mcp-public/portal-bulk.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.00009 | $0.00350 |
| Opus 5 | $0.00005 | $0.00175 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
portal-bulk 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 12d 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 portal-bulk — 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
Apply a change across many blocks/pages — guarded. Change: $ARGUMENTS
Confirm a portal is connected: check_connection (one call — portal, version, identity, write posture, browser assist). If it reports connected:false, relay its reason + fix and send the user to /portal-setup.
Launch the portal-bulk-operator agent (via the Task tool) with the change above, and require this sequence:
- Snapshot first —
snapshot_portalbefore any write, so the whole batch is revertible (restore_resource). - Dry-run plan — identify every affected block/page and present the exact intended change as a plan. Use one declarative
place_blockscall for page reordering/placement (atomic read-modify-write;mode:"merge"to add/update/remove,mode:"replace"+confirm:truefor an exact list) — never a series of racing per-block placement writes. Anyupdate_blockon a bound block must re-send its existingui_queriesor the binding is wiped. - Get explicit confirmation BEFORE applying. Do not write anything until the user approves the dry-run plan.
- Apply, then verify — re-read a sample of the changed resources to confirm the change landed and nothing was blanked.
- Report rollback — state the snapshot handle and exactly how to revert.
Finish with: what changed (counts + scope), verification result, and the rollback handle.
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.
- 12d ago First seen · 21 lines · 9 tokens per session scan A fbb0caf8293b
portal-bulk is a command published in the GitHub repository zuarbase/Zuar-Portal-MCP-Public (0 stars, last pushed 9d ago), licensed MIT. It adds 9 tokens to every session and 350 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to portal-bulk, differing in 0 lines, and is treated as a copy.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.