Berd is an open-source desktop application for working with AI agents through a graphical interface. It is intended for people who want to use different AI models and an integrated Goose backend from a desktop app. The catalogue entries add agent skills, agents, and instructions for working within Berd.
Borrowing it
Nothing to install: this file belongs to block/berd. 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/block/berd/main/.agents/skills/berdctl-new-command/SKILL.mdgit clone --depth 1 https://github.com/block/berdWrote 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/block/berd/berdctl-new-command)<a href="https://agentmods.dev/skills/block/berd/berdctl-new-command"><img src="https://agentmods.dev/badge/skills/block/berd/berdctl-new-command/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/block/berd/berdctl-new-command"><img src="https://agentmods.dev/badge/skills/block/berd/berdctl-new-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 34 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00037 | $0.00538 |
| Opus 5.5 | $0.00015 | $0.00215 |
| Sonnet 5.5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
berdctl-new-command 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
berdctl command changes
One command is one renderer module. Descriptors are the source for zod
validation, TS input types, CLI help, and generated contract JSON. Background:
docs/berdctl-architecture.md.
Rules
- Verbs must be UI-visible. Prefer reversible mutations, but one-way visible product actions like creating a session or sending a prompt are allowed. Delete, bulk, silent, invisible, or broadly destructive work requires auth/confirmation design review.
- Put bounds in zod; clap mirrors them.
- Keep descriptors import-pure. Import stores, Tauri APIs, navigation,
providers, and caches only inside
execute/precheck. - Do not hand-edit generated contract JSON.
- Keep the broker command-agnostic; normal command changes do not touch
src-tauri/plugins/berdctl/. - Breaking wire reshapes bump both discovery.rs constants and the contract mirror. New commands and optional fields are not reshapes.
Workflow
- Add commands with
just new-command <noun> <verb>. - Implement
src/features/berdctl/commands/impl/<verbNoun>.tswith:.strict()schema,.describe()on every field,summary,description,helpFooter, safety metadata, optionalprecheck, andexecute. - Update inventories only when needed:
registry.tsgroupcli.about, top-level help pins intree.rs, anddistro/skills/berdctl/SKILL.mdfor overview changes. - Run
pnpm generate:berdctl-contract,pnpm vitest run src/features/berdctl, andcargo test -p berdctlfromsrc-tauri/. - Before review, confirm the verb is UI-visible and either reversible or a direct visible product action, help is complete, error messages name the fixing command, artifacts are regenerated, and tests cover the behavior.
Keep CLI shapes expressible by the generated field walker. If a requested
operation needs an explicit null or another shape that generic flags cannot
represent safely, model it as a separate command action instead of adding
command-specific Rust mapping. Example: use session move --project-id <id>
for moving into a project and session clear-project for moving out.
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.
- 1mo ago First seen · 48 lines · 37 tokens per session scan A 8c6435c046dd
berdctl-new-command is a skill published in the GitHub repository block/berd (1,007 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 538 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.