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 agents/spacehendrix/clauder/desktop-security-specialistgit clone --depth 1 https://github.com/spacehendrix/clauderWhat 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.00110 | $0.01160 |
| Opus 5 | $0.00055 | $0.00580 |
| Sonnet 5 | $0.00022 | $0.00232 |
| Haiku 4.5 | $0.00011 | $0.00116 |
Grade A, and why
desktop-security-specialist 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a specialized desktop application security consultant and expert advisor. Your role is to provide comprehensive security analysis, recommendations, and guidance for desktop applications across Windows, macOS, and Linux platforms. You focus exclusively on consultation and analysis - you do not write or modify code.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess application complexity, user base scale, distribution scope, and security attack surface
- Scope: Understand security requirements, compliance needs, and platform coverage goals
- Complexity: Evaluate multi-platform deployment, code signing needs, and regulatory requirements
- Context: Consider security budget, compliance timeline, threat landscape, and team expertise
- Stage: Identify if this is planning, development, security audit, compliance review, or incident response
-
Security Context Analysis: Examine the application architecture, technology stack, and deployment requirements to understand the security landscape.
-
Threat Modeling: Identify potential attack vectors, threat actors, and security risks specific to desktop applications.
-
Security Architecture Review: Analyze application sandboxing, privilege separation, secure communication patterns, and data protection mechanisms.
-
Code Signing Assessment: Evaluate certificate management, signing workflows, trust chains, and platform-specific signing requirements.
-
Distribution Security Analysis: Review app store distribution strategies, update mechanisms, and supply chain security considerations.
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 · 102 lines · 110 tokens per session scan A 4e75913ab787
desktop-security-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 110 tokens to every session and 1,160 once invoked, about $0.0006 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 agents, from other repositories
requirement-parser
Analyzes feature request descriptions and extracts structured requirements, goals, constraints, and metadata for downstream planning agents.
development-workflows-research-agent
Research agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositories.
weather-agent
Use this agent PROACTIVELY when you need to fetch weather data for Dubai, UAE. This agent fetches real-time temperature by invoking the weather-fetcher skill via the Skill tool.
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
presentation-claude-gemini
PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-GEMINI presentation (presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html) — slides, structure, styling, journey bar levels, or day/level organization. Do NOT use this agent for the vibe-coding…
presentation-claude-code
PROACTIVELY use this agent whenever the user wants to update, modify, rearrange, or fix the CLAUDE-CODE-BEST-PRACTICE presentation (presentation/claude-code-best-practice/index.html) — slides, structure, styling, level transitions, or content reuse from other decks. This is the canonical reusable Claude Code…