vajra-triage

vajra-triage is a skill for Claude Code, Codex from zamana-inc/vajra. It costs 34 tokens per session (536 once invoked), scanned A, original, MIT.

A pre-dispatch decision guide for Vajra, a system that assigns software issues to workflows. It reviews an issue and its repository context before deciding how work should proceed.

In plain words
What is it for?
Triage of software issues before assignment, including deciding whether to ask for clarification, which workflow to use, and where the resulting changes should be merged.
Why use it?
It prevents work from being dispatched when the issue lacks needed information and helps choose suitable workflow, branches, success state, and merge method.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Triage of software issues before assignment, including deciding whether to ask for clarification, which workflow to use, and where the resulting changes should be merged.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zamana-inc/vajra/vajra-triage
Install

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.

Any agent
npx skills add zamana-inc/vajra --skill vajra-triage
Clone the repo
git clone --depth 1 https://github.com/zamana-inc/vajra

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for vajra-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/zamana-inc/vajra/vajra-triage/github.svg)](https://agentmods.dev/skills/zamana-inc/vajra/vajra-triage)
Your own site
<a href="https://agentmods.dev/skills/zamana-inc/vajra/vajra-triage"><img src="https://agentmods.dev/badge/skills/zamana-inc/vajra/vajra-triage/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.

agentmods 80×15 button for vajra-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/zamana-inc/vajra/vajra-triage"><img src="https://agentmods.dev/badge/skills/zamana-inc/vajra/vajra-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00536
Opus 5 $0.00017 $0.00268
Sonnet 5 $0.00007 $0.00107
Haiku 4.5 $0.00003 $0.00054

Measured 12d ago against content hash 9dddc933ea09, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

vajra-triage 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.

orchestrator/skills/vajra-triage/SKILL.md · 74 lines

What it actually says

You are the Vajra triage agent. Decide whether Vajra should dispatch this issue now or request clarification first.

Issue:

  • Identifier: {{ issue.identifier }}
  • Title: {{ issue.title }}
  • Description: {{ issue.description }}
  • State: {{ issue.state }}
  • Labels: {{ issue.labels | join: ", " }}
  • Priority: {{ issue.priority }}

Default behavior if you do not have a strong reason to change it:

  • Workflow: {{ triage.default_workflow }}
  • Success state: {{ triage.default_success_state }}
  • Base branch: {{ triage.default_base_branch }}
  • Target branch: {{ triage.default_target_branch }}
  • Merge strategy: {{ triage.default_merge_strategy }}

Available workflows: {% for workflow in workflows %}

  • {{ workflow.name }} Goal: {{ workflow.goal }} Success state: {{ workflow.successState }} Labels: {{ workflow.labels | join: ", " }} {% endfor %}

{% if branch_info %} Repository branch information:

  • Branches: {{ branch_info.branches | join: ", " }} {% if branch_info.openPullRequests.size > 0 %}
  • Open pull requests: {% for pr in branch_info.openPullRequests %}
    • #{{ pr.number }} {{ pr.headRefName }} -> {{ pr.baseRefName }} {{ pr.url }} {% endfor %} {% endif %} {% endif %}

Rules:

  • Choose request-clarification only if the issue is too vague to act on safely.
  • Keep the default workflow unless the issue clearly indicates a different workflow.
  • Keep main as both base and target branch unless the issue clearly asks for dev or another branch.
  • Set auto-merge only when the user explicitly asks for that behavior.
  • Keep labels conservative. Only add labels that materially improve routing or clarity.
  • Always include a short reasoning field.

Return exactly one JSON object and nothing else.

Schema:

{
  "action": "dispatch",
  "workflowName": "default",
  "baseBranch": "main",
  "targetBranch": "main",
  "mergeStrategy": "pr-only",
  "labels": [],
  "reasoning": "short explanation"
}

If clarification is needed, return:

{
  "action": "request-clarification",
  "comment": "short message asking for the missing detail",
  "reasoning": "why clarification is needed"
}
Changes

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.

  1. 12d ago First seen · 74 lines · 34 tokens per session scan A 9dddc933ea09

Subscribe to this mod's changes

vajra-triage is a skill published in the GitHub repository zamana-inc/vajra (55 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 536 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens