Borrowing it
Nothing to install: this file belongs to yzonur/sap-adt-mcp. 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/yzonur/sap-adt-mcp/main/.claude/commands/panel.mdgit clone --depth 1 https://github.com/yzonur/sap-adt-mcpWrote 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/yzonur/sap-adt-mcp/panel)<a href="https://agentmods.dev/commands/yzonur/sap-adt-mcp/panel"><img src="https://agentmods.dev/badge/commands/yzonur/sap-adt-mcp/panel/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/yzonur/sap-adt-mcp/panel"><img src="https://agentmods.dev/badge/commands/yzonur/sap-adt-mcp/panel.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.00015 | $0.00201 |
| Opus 5 | $0.00008 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
panel 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
Call the adt_open_panel MCP tool (from the sap-adt-mcp server) to start the
local read-only control panel and open it in the browser.
- If the user passed
close/kapatas an argument, calladt_close_panelinstead and confirm it stopped. - If the user passed
url/nourl, calladt_open_panelwith{ "open": false }and just report the URL without opening a browser. - Otherwise call
adt_open_panelwith no arguments (opens the browser).
After the tool returns, tell the user the panel URL in one line and remind them it stays up only while this session keeps the MCP connected. If the tool errors because the sap-adt-mcp MCP isn't connected in this session, say so plainly.
Arguments (optional): $ARGUMENTS
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 · 19 lines · 15 tokens per session scan A b1c5cc470441
panel is a command published in the GitHub repository yzonur/sap-adt-mcp (15 stars, last pushed 22d ago), licensed MIT. It adds 15 tokens to every session and 201 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-30.
Other commands, from other repositories
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.