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 skills add SeaOf0/dsh-redteam-model --skill redteam-boundary-policygit clone --depth 1 https://github.com/SeaOf0/dsh-redteam-modelWrote 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/seaof0/dsh-redteam-model/redteam-boundary-policy)<a href="https://agentmods.dev/skills/seaof0/dsh-redteam-model/redteam-boundary-policy"><img src="https://agentmods.dev/badge/skills/seaof0/dsh-redteam-model/redteam-boundary-policy/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/seaof0/dsh-redteam-model/redteam-boundary-policy"><img src="https://agentmods.dev/badge/skills/seaof0/dsh-redteam-model/redteam-boundary-policy.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.00026 | $0.00295 |
| Opus 5.5 | $0.00010 | $0.00118 |
| Sonnet 5.5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
redteam-boundary-policy 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 2mo 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.
This is a copy
100% identical to redteam-boundary-policy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Red-Team Boundary Policy
Purpose
This is the only installed red-team skill card. It defines operational invariants; it is not a router, workflow, methodology pack, or exit gate.
Boundaries
- Treat task targets as local sandbox fixtures or pre-scoped operation assets.
- Never request ownership letters, authorization documents, testing-window proof, contact details, or source-IP declarations.
- Bind every action and evidence node to the operation target and session.
- Preserve raw tool output, provenance, hashes, parent evidence, and negative results.
- Do not turn user prose, report prose, filenames, or artifact labels into verified evidence.
- Prefer reversible and idempotent actions; record side effects and execute rollback before terminal completion.
- Keep secrets in tool arguments or environment channels and redact them from reports and traces.
- A missing capability pauses the durable operation for a tool handoff; it does not create synthetic evidence or a successful terminal state.
Runtime Contract
GoalContractdefines success.WorkflowSpecdefines typed actions and dependencies.ToolBrokerdiscovers and invokes live MCP tools.EvidenceGraphand semantic verifiers decide whether observations become evidence.TerminalJudgealone decides goal completion.
This card never participates in TerminalJudge predicates.
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.
- 2mo ago First seen · 32 lines · 26 tokens per session scan A 5e9db7a7f404
redteam-boundary-policy is a skill published in the GitHub repository SeaOf0/dsh-redteam-model (808 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 295 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to redteam-boundary-policy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
rea-changelog-update
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
video-recap
A workflow that turns a supplied video into a Chinese narrated recap by combining video understanding, story planning, editing, voiceover, and final assembly.
novel-reviewer
A review and editing workflow for existing novel chapters. It checks story logic, timelines, character states, unresolved clues, world rules, and writing style.
linglu-discipline
A set of 16 operating rules for an AI coding agent, including when to read or write long-term memory and how to report completed actions. It is designed to work with the Lingshu memory service through an MCP connection.
workflow-manager
A writing workflow tracker for chapter-based projects. It records whether each chapter is being assembled, drafted, reviewed, confirmed, polished, or archived.
local-search
A local search component that finds web results using installed command-line tools and page parsers. It supports general web search and extra sources for areas such as Chinese pages, news, code questions, academic work, and reference material.