Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add umangbuilds/dhurandhar-os/plugin install dhurandhar-osWrote 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/umangbuilds/dhurandhar-os/using-dhurandhar)<a href="https://agentmods.dev/skills/umangbuilds/dhurandhar-os/using-dhurandhar"><img src="https://agentmods.dev/badge/skills/umangbuilds/dhurandhar-os/using-dhurandhar/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/umangbuilds/dhurandhar-os/using-dhurandhar"><img src="https://agentmods.dev/badge/skills/umangbuilds/dhurandhar-os/using-dhurandhar.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.00112 | $0.01548 |
| Opus 5 | $0.00056 | $0.00774 |
| Sonnet 5 | $0.00022 | $0.00310 |
| Haiku 4.5 | $0.00011 | $0.00155 |
Grade A, and why
using-dhurandhar 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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using DhurandharOS
The orchestration layer for the seven DhurandharOS Tier 1 skills. Use this routing table on every user message before deciding which skill to load.
Skill routing — use the right skill for each request
| Skill | Triggers on |
|---|---|
| Soul Keeper | Always active. Identity and voice layer. Auto-loaded via SessionStart hook. |
| Workflow Orchestrator | Raw build intent BEFORE a spec exists — "I want to build X", "let's build X", "help me make X", "create a tool that X", "I have an idea for X", "can we build X", "I want to make X", "build me X". Walks the operator through reality-check → PRD → build → review → launch with explicit checkpoints. Does NOT fire if a PRD already exists or on meta-prompts about DhurandharOS itself. |
| Idea + Reality Check | "should I...", "thinking about...", "what if...", "I'm considering...", "pivoting...", "not sure if...", risky decisions, overcomplicated plans. Also invoked by Workflow Orchestrator as step 1. Refuses to ship code without first paying users named. |
| PRD Writer | "spec this", "write requirements", "PRD", "let's design the feature", "scope this", "lock the spec". Also invoked by Workflow Orchestrator as step 2. |
| Builder | Spec-to-code only — "implement the spec", "build per the PRD", "code this up based on the spec", "let's code", "ship the spec", "write the function" / "create the endpoint" when a spec is in scope. Does NOT fire on raw build intent (those go to Workflow Orchestrator first). Also invoked by Workflow Orchestrator as step 3. |
| UI Designer | Visual polish on EXISTING artifacts — "make this look good", "fix the design", "this looks ugly", "redesign", "improve the UI", "the UX feels off". AND auto-invoked by Builder for any task that produces HTML/CSS/JSX output. Does NOT fire on raw build intent for new ideas — "create a web page for X", "build a landing page for X", "design a page for X" route to Workflow Orchestrator first. Builder handles logic; UI Designer handles aesthetics. UI Designer's visual decisions override Builder's defaults. |
| Reviewer | "review this", "check this code", "is this safe?", git diff, PR creation — AND automatically after Builder completes ANY build task. |
| Deployment Advisor | "deploy", "hosting", "where should I host", "what infra", "cloud setup", "going live", "production setup", "Vercel", "Supabase", "AWS", "scaling". |
| Launch + Marketer | "help me launch", "write copy", marketing/launch requests. v0.1 stub — responds with "coming in v0.2" and points to coreyhaines31/marketingskills. |
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.
- 12d ago First seen · 68 lines · 112 tokens per session scan A 8d8f53896aac
using-dhurandhar is a skill published in the GitHub repository umangbuilds/dhurandhar-os (1 stars, last pushed 4mo ago), licensed MIT. It adds 112 tokens to every session and 1,548 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…