Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add matebenyovszky/agentplaybooks/plugin install agentplaybooksWrote 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/matebenyovszky/agentplaybooks/push)<a href="https://agentmods.dev/commands/matebenyovszky/agentplaybooks/push"><img src="https://agentmods.dev/badge/commands/matebenyovszky/agentplaybooks/push/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/matebenyovszky/agentplaybooks/push"><img src="https://agentmods.dev/badge/commands/matebenyovszky/agentplaybooks/push.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.00013 | $0.00335 |
| Opus 5 | $0.00006 | $0.00168 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
push 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 9d 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.
What it actually says
Push the local playbook to the linked (or a new) remote playbook.
- Run:
node "${CLAUDE_PLUGIN_ROOT}/bin/agentplaybooks.js" push $ARGUMENTS --jsonIf it fails with a missing-key error, ask the user to runagentplaybooks login(or setAGENTPLAYBOOKS_API_KEY) first — never ask them to paste the key into the chat. - Summarize the plan: playbook create/update, instruction-file upload, skill
creates/updates, MCP server creates/updates, and any skipped conflicts.
An instruction conflict means the project-root
AGENTS.mdandCLAUDE.mddisagree — the fix is to make one import the other, never to copy text. Note that remote entries missing locally are left untouched, that hosted-only MCP settings (timeouts, auth, curated tool lists, descriptions) are preserved rather than overwritten, and that no secret values are ever uploaded. - If the CLI refuses because of likely hard-coded credentials, help the user
move the values to environment references (
${VAR}) and re-plan — do not bypass it. The reference then appears in the manifest'sspec.secrets, which is how a teammate learns what to set. - Only after the user confirms, re-run with
--applyand report the playbook GUID so teammates canpullit.
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.
- 9d ago First seen · 25 lines · 13 tokens per session scan A 85a9c73cbcbd
push is a command published in the GitHub repository matebenyovszky/agentplaybooks (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 335 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
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
TODO
The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra.
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.