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/agentlas-ai/agentlas-desktop/provenpx skills add agentlas-ai/agentlas-desktop --skill provegit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/prove)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/prove"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/prove.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.00121 |
| Opus 5 | $0.00006 | $0.00060 |
| Sonnet 5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
prove 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 5d 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
Steps
- Refresh the installed plugin router cache and ask the host for the explicit plugin prompt block.
- Confirm the router body is present for the installed mention.
- Invoke the simplest workflow with a concrete proof input and retain its runtime summary.
Outputs
- A proof receipt that distinguishes proven from installed-but-unproven.
Verification
- Router injection is true.
- The workflow run is completed with a non-empty summary; missing tools or runtimes remain an explicit unproven result.
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.
- 5d ago First seen · 20 lines · 12 tokens per session scan A 0e3bb0b3c0ef
prove is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 121 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 skills, from other repositories
create-workspace
Creates a .clave workspace file that defines groups, sessions, terminals, toolbar actions, and icons for the Clave desktop app. Use when the user wants to create, edit, or understand .clave workspace files.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
recover-sessions
Rebuilds a lost Clave workspace by finding the user's past Claude Code sessions on disk, mapping them to projects, and reopening them as grouped tabs with their full history. Use when the user has lost their tabs or groups (crash, restart, accidental close) and wants their working sessions back, or when they ask what…
ensemblr
How Ensemblr works from inside it — the workspace/git-worktree model, the ensemblr control tools and what their answers mean, the committed .ensemblr/settings.toml (setup and run scripts, [git], [prompts], [infisical], environment variables), /.config/ensemblr/config.json, the Changes panel and diff comments, the…
skills-cli-sync
Sync skills-desktop's AGENTDEFINITIONS and UNIVERSALAGENTIDS with the upstream vercel-labs/skills CLI, then update docs and validate. Use when bumping SKILLSCLIVERSION, mirroring a new upstream skills-CLI release, or when the agent list / universal set drifts from upstream agents.ts.
react-doctor
Use when finishing a feature, fixing a bug, before committing React code, or when the user types /doctor, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.