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 agentmods add skills/markus-global/markus/markus-admin-clinpx skills add markus-global/markus --skill markus-admin-cligit clone --depth 1 https://github.com/markus-global/markusWhat 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 | $0.00023 | $0.00537 |
| Opus 5 | $0.00012 | $0.00269 |
| Sonnet 5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
markus-admin-cli 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 2d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Administration via CLI
NOTE: The CLI is intentionally minimal. Most operations should be done through built-in agent tools or the Web UI. The CLI is reserved for infrastructure bootstrap, human-agent communication, and emergency operations.
How to invoke
Use markus via shell_execute. The binary is automatically available in PATH.
markus admin system status --json
Always use --json when parsing results programmatically. The CLI connects to http://localhost:8056 by default. Override with --server <url> or MARKUS_API_URL. For authenticated access use --api-key <key> or MARKUS_API_KEY.
Available Admin Commands
markus admin system status --json
markus admin system version --json
markus admin system update
markus admin system update --dry-run
markus admin system emergency-stop
| Command | Description |
|---|---|
admin system status |
System and health status |
admin system version |
Current version, git info, and whether updates are available |
admin system update |
Pull latest code, install deps, rebuild. --dry-run to preview |
admin system emergency-stop |
Immediately stop all agents |
Update Workflow
When updating the platform: (1) confirm with the user, (2) run markus admin system update, (3) restart the service with markus start.
Other CLI Commands (non-admin)
markus start # Start the server
markus doctor # Diagnose configuration
markus model # Configure LLM providers
markus models [provider] # List available models
markus auth list|add|remove # Manage API credentials
markus install <platform> # Install external agent platform
markus agent list # List agents
markus agent get <id> # Get agent details
markus agent chat <id> # Interactive chat
markus agent message <id> # Send one-shot message
Prefer Built-in Tools
For project, task, requirement, deliverable, team, and skill management, always use built-in agent tools (task_create, list_projects, requirement_propose, team_list, etc.) instead of CLI commands. The CLI does not provide these commands — they are agent-only operations.
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.
- 2d ago First seen · 59 lines · 23 tokens per session scan A dbe975a43efa
markus-admin-cli is a skill published in the GitHub repository markus-global/markus (157 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 537 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 skills, from other repositories
dashclaw-ship
The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every description of the…
dashclaw-governance
Governance behavior for AI agents governed by DashClaw. Teaches the governance protocol: when to call guard (risk thresholds), how to interpret decisions (allow/warn/block/requireapproval), when to record actions, how to wait for approvals, and session lifecycle management. Loads org-specific policies and capabilities…
instrument-agent
Integrate DashClaw SDK into any agent using the 4-step governance loop.
troubleshoot
Debug DashClaw errors, signal issues, and misconfigurations.
compliance-drift-evals
Set up compliance exports, drift detection, evaluations, scoring, and learning analytics.
build-dashclaw
Contribute to the DashClaw codebase — architecture, scaffolding, tests, CI.