Agent skill

Priority Board Triage

by samugit83 in samugit83/redamon

The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer.

MITAuto-check passedSecurity

Install Priority Board Triage

skills CLI
$ npx skills add samugit83/redamon --skill priority-board-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install samugit83/redamon priority-board-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/samugit83/redamon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/priority-board-triage .claude/skills/priority-board-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
priority-board-triage
GitHub stars
3k
Token cost
~1.7k tokens
SKILL.md length
572 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer.

  • Tasks that involve Penetration testing
  • SKILL.md covers When to Use, Critical Rules, Pattern: a writer asks combine… and Commands, plus 1 more section
  • Calls npx
  • Tasks that involve MCP servers

What it does

Priority Board Triage is an agent skill from samugit83/redamon. The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer. A writer that sets a final score itself, or touches another layer, silently undoes a review or a person's verdict at the next run. Trigger: editing agentic/cypherfixtriage/ (scoremodel, layers, evidence, orchestrator, findingops, prompts/review.py); editing triagemixin.py; editing webapp/src/lib/triage/, the /api/triage routes, the Triage board components, or the…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Penetration testing and MCP servers. It works with Model Context Protocol. The repository describes itself as: Open-source, self-hosted AI penetration testing framework: maps your attack surface into a graph, autonomously exploits it from a Kali sandbox with human approval gates, and… The licence is MIT.

When your agent uses it

  • Tasks that involve Penetration testing
  • Tasks that involve MCP servers

Example prompts

  • “/priority-board-triage”

Requirements

  • Python 3
  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit d90c940. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Priority Board Triage loads about 1.7k tokens when it runs. Until then it costs about 149 tokens; SKILL.md has 572 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from samugit83/redamon at commit d90c940, republished under its MIT licence (© samugit83). 572 words, ~1,692 tokens.

Download SKILL.mdSave it as .claude/skills/priority-board-triage/SKILL.md (or your agent's skills folder).
name
priority-board-triage
description
The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer. A writer that sets a final score itself, or touches another layer, silently undoes a review or a person's verdict at the next run. Trigger: editing agentic/cypherfix_triage/ (score_model, layers, evidence, orchestrator, finding_ops, prompts/review.py); editing triage_mixin.py; editing webapp/src/lib/triage/, the /api/triage routes, the Triage board components, or the MCP triage tools (triageTools.ts, verdictTools.ts).
license
MIT
metadata.author
redamon
metadata.version
1.0.0
metadata.scope
root, agentic, webapp
metadata.auto_invoke
Changing how a triage score, review or verdict is computed or written, Editing the Priority Board, the triage graph mixin, or the MCP triage tools

When to Use

  • Changing the risk model, the evidence bundle, the review prompt or its validation.
  • Adding a writer of any triage_* property: a run step, a route, an MCP tool, a migration.
  • Adding a reader of the board state: a report, an MCP tool, a filter, a UI chip.

For the Cypher itself, also follow graph-db-writes; for a new MCP tool, mcp-server-tools.


Critical Rules

  • NOBODY writes a final score. triage_priority_score, triage_tier, triage_tier_rule, triage_risk, triage_factors, triage_state and triage_decided_by (the mixin's _FINAL_SET) come ONLY from score_model.combine_layers(), reached through layers.combine_props(). A writer changes ITS layer and asks combine for the final inside the same transaction. Setting a final directly is how a review or a verdict used to vanish at the next run.

  • Each writer touches one layer.

    WriterLayerMethod
    a run's publishBASE (+ a builtin REVIEW it made)publish_triage_layers
    an MCP agent's reviewREVIEW, channel mcpwrite_review
    a person (app, or MCP with channel mcp)DECISIONset_human_verdict

    A publish never writes a decision, :Muted or updated_at; a review never writes a decision or the base; a verdict never writes the base or a review.

  • NEVER write updated_at from triage. It is the scan's "last seen" stamp: the prune reads it, and the publish's guard skips a node whose updated_at moved since the run read it. A triage write that bumped it would make every finding look re-ingested.

  • Every single-finding write is lock-then-read, in one managed transaction. SET n._triage_lock = true REMOVE n._triage_lock first, then read the node, the live proof (_LIVE_PROOF) and the current layers, then decide and write. Match exactly one node, else ambiguous. A timeout raises TriageWriteBusy, which the API returns as 503 busy. Never read proof from a run's snapshot.

  • Live proof is proof of THIS finding. _LIVE_PROOF mirrors score_model.is_proven; it must not read triage_proof, which records proof on the finding's HOST. Reading it lifted every finding on a compromised host to T1 "proven" at its next rescore. (The mute guards' _PROVEN does read it, on purpose: refusing a mute on a compromised host is the safe direction.)

  • An app decision is never changed or reset over MCP (decided_in_app). Only app-channel decisions by the user themself teach a detector's prior.

  • A review is valid only while triage_ai_evidence_hash == triage_evidence_hash. The hash is bundle_hash(build_bundle(...)): normalised, secret-redacted, capped. Changing the bundle, the redaction or the cap changes every hash and expires every review: bump REVIEW_PROMPT_VERSION deliberately, never by accident.

  • A run never reviews over a valid mcp review, and re-reviews its own (builtin) only on a model or prompt-version change. Fix-item text (fix_lever, ai_quote) comes from builtin reviews only.

  • Keep the legacy readers tolerant. Unknown or legacy values mean "no layer", never a decision. triage_source = 'ai' is a builtin false-positive review; a missing triage_verdict_channel means app. The first publish after an upgrade adopts an unchanged review-v1 review through build_bundle_legacy, and unmute applies the same cleanup to muted nodes. Readers that branch on this: score_model.finding_state, reportData.ts, projectRisk.ts, tooling/scripts/triage_eval.py.

  • A new stored triage_* property goes in TRIAGE_PROPS (triage_mixin.py), which feeds triage_graph_migrate.py, and in TRIAGE_PROPERTIES (webapp/src/lib/triage/properties.ts), which keeps it out of the Recon Delta. Agent-writable text also goes in TRIAGE_TEXT_PROPERTIES, so buildNodeContext never hands it to the in-app agent. Declare it in graph_db/schema_sections.md and re-seed the catalog.

Show full SKILL.md (39 more words)Show less

Pattern: a writer asks combine for the final

python
# graph_db/mixins/recon/triage_mixin.py - write_review, trimmed
def work(tx):
    found = self._lock_findings(tx, user_id, project_id, node_id, label)  # lock, THEN read
    ...                                                  # not_found / ambiguous
    props = dict(rec["props"])
    outcome = decide(props, rec["proven_now"], rec["updated_at"], rec["label"])
    if outcome.get("refused"):
        return {"written": False, "reason": outcome["refused"]}   # nothing written
    review = self._clean_review(outcome["review"])       # only THIS layer's keys
    tx.run("MATCH (n) WHERE elementId(n) = $eid SET n += $review", ...)
    props.update(review)
    final = self._clean_final(combine(props, rec["proven_now"]))  # layers.combine_props
    tx.run(f"MATCH (n) WHERE elementId(n) = $eid SET {self._FINAL_SET}", ...)
return self._write_tx(self.driver, work, timeout)       # TriageWriteBusy on timeout

Commands

bash
./agentic/run_tests.sh tests/test_score_model.py          # combine_layers + the model
./agentic/run_tests.sh tests/test_triage_orchestrator_flow.py
./agentic/run_tests.sh tests/test_triage_finding_ops.py
# root tests run in the agent image; the *_live suites need Neo4j and self-skip without it
./redamon.sh test unit
cd webapp && npx vitest run src/lib/triage src/lib/mcp src/app/api/triage

Resources

© samugit83, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/priority-board-triage of samugit83/redamon.

Open the folder on GitHubat commit d90c940

Compare with similar skills

Priority Board Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Priority Board Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Priority Board Triage this skillsamugit83/redamon3k—~1.7kAutomated safety check: PassMIT
Burp Scansix2dez/burp-ai-agent1.5k—~6.4kAutomated safety check: WarnMIT
Burp MCP Vuln Checklangbyyi/CyberStrikeAI-SRC134—~3.1kAutomated safety check: PassApache-2.0
Hunt BurpEncod3d-Sec/TORCH3291 repos~3.1kAutomated safety check: PassMIT
Golang Pkg Go Devcontext-labs/whip1.1k2 repos~3kAutomated safety check: PassMIT
Forensifyalexgreensh/repo-forensics188—~2.5kAutomated safety check: NotesCustom licence

Similar skills

  • Burp Scan

    six2dez/burp-ai-agent

    Burp Suite scanning via MCP tools — passive traffic analysis, active payload testing, OOB verification, and vulnerability reporting using Burp's proxy, HTTP sender, Collaborator, and scanner APIs.

    1.5k GitHub stars~6.4k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings
  • Burp MCP Vuln Check

    langbyyi/CyberStrikeAI-SRC

    Automate low-impact web vulnerability verification through Burp MCP.

    134 GitHub stars~3.1k tokensUpdated yesterday
    SecurityAuto-check passed
  • Hunt Burp

    Encod3d-Sec/TORCH

    Drive Burp Suite over its MCP server as an AI triage + attack layer - review proxy history for signals, replay via Repeater/send, OOB-gate blind bugs with Collaborator, fuzz via Intruder (RoE-safe)…

    329 GitHub starsUsed in 1 repo~3.1k tokens
    SecurityAuto-check passed
  • Golang Pkg Go Dev

    context-labs/whip

    Golang package/module docs via godig, a pkg.go.dev API client (CLI + MCP) — APIs, symbols, versions, importers, licenses, vulnerabilities.

    1.1k GitHub starsUsed in 2 repos~3k tokens
    SecurityAuto-check passed
  • Forensify

    alexgreensh/repo-forensics

    Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.

    188 GitHub stars~2.5k tokensUpdated 11 days ago
    SecurityAuto-check: notes
  • Review Security Report

    PrefectHQ/fastmcp

    Review FastMCP vulnerability reports before accepting, rejecting, patching, scoring, or publishing them.

    28k GitHub stars~1.2k tokensUpdated yesterday
    SecurityAuto-check passed

More from samugit83/redamon

All 15 skills in this repo
  • Add Community Skill

    samugit83/redamon

    Adding a Community Agent Skill: a Markdown attack-workflow file that users import from the catalog, which then competes in the Intent Router and is injected into the agent's system prompt.

    3k GitHub stars~775 tokensUpdated yesterday
    Auto-check passed
  • Add Partial Recon

    samugit83/redamon

    Adding partial-recon support for a tool: running a single pipeline phase on demand from the workflow graph, reading its inputs from the existing Neo4j graph and merging results back.

    3k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Agentic Tool Integration

    samugit83/redamon

    Wiring a new tool the AI agent can call (not the recon pipeline): the tool registry, the phase map, the hardcoded dispatch chokepoint, and the duplicated execution paths that make a tool work in…

    3k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Builtin Agent Skill

    samugit83/redamon

    Adding a built-in Agent Skill (an attack technique like ssrf, xxe, rce) that ships hardcoded in RedAmon: classified by the Intent Router, injected into the agent prompt, toggled per project, badged…

    3k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Graph DB Writes

    samugit83/redamon

    Writing to the Neo4j attack-surface graph in RedAmon: the tenant-isolation MERGE key every entity node must carry, where graph methods live (mixins, not the client), and the schema places that must…

    3k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • LLM Provider Integration

    samugit83/redamon

    Adding an LLM provider to RedAmon: the credential boundary (keys must never reach scan containers), prefix-routed model ids, and the provider registry.

    3k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Priority Board Triage

What does Priority Board Triage do?

The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer. Priority Board Triage is an agent skill from samugit83/redamon. The Priority Board's three-layer score model (rules BASE, REVIEW by the built-in AI or an MCP agent, a person's DECISION) and who may write which layer.

When should I use Priority Board Triage?

Priority Board Triage fits situations like: tasks that involve Penetration testing; tasks that involve MCP servers.

How do I install Priority Board Triage in Claude Code?

Run `npx skills add samugit83/redamon --skill priority-board-triage -a claude-code`. Or copy the skill folder (skills/priority-board-triage in samugit83/redamon) into .claude/skills/priority-board-triage in your project. Claude Code loads it when a task matches its description.

How do I install Priority Board Triage in Codex?

Run `npx skills add samugit83/redamon --skill priority-board-triage -a codex`. Or copy the skill folder (skills/priority-board-triage in samugit83/redamon) into .agents/skills/priority-board-triage in your project. Codex loads it when a task matches its description.

Can I use Priority Board Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samugit83/redamon --skill priority-board-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/priority-board-triage, .gemini/skills/priority-board-triage, .github/skills/priority-board-triage and .opencode/skills/priority-board-triage in your project.

What does Priority Board Triage need to run?

Going by SKILL.md and its folder, Priority Board Triage needs the command-line tools its instructions call (npx). Our summary lists: Python 3; Node.js.

Does Priority Board Triage access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Priority Board Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Priority Board Triage use?

Priority Board Triage is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Priority Board Triage use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Priority Board Triage?

Skills that share tags, products or a category with Priority Board Triage: Burp Scan (six2dez/burp-ai-agent, 1.5k stars), Burp MCP Vuln Check (langbyyi/CyberStrikeAI-SRC, 134 stars), Hunt Burp (Encod3d-Sec/TORCH, 329 stars) and Golang Pkg Go Dev (context-labs/whip, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Priority Board Triage?

samugit83 (a GitHub user) maintains it in samugit83/redamon, which has 2,961 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: samugit83/redamon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.