Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/WARROOM-CEO/COREnpx agentmods add skills/warroom-ceo/core/triage-ndaWrote 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/warroom-ceo/core/triage-nda)<a href="https://agentmods.dev/skills/warroom-ceo/core/triage-nda"><img src="https://agentmods.dev/badge/skills/warroom-ceo/core/triage-nda/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/warroom-ceo/core/triage-nda"><img src="https://agentmods.dev/badge/skills/warroom-ceo/core/triage-nda.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.00118 | $0.03211 |
| Opus 5.5 | $0.00047 | $0.01284 |
| Sonnet 5.5 | $0.00024 | $0.00642 |
| Haiku 4.5 | $0.00012 | $0.00321 |
Grade A, and why
triage-nda-th 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 1mo 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
92% identical to triage-nda — 14 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.
/triage-nda -- NDA-th Pre-Screening-th
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Triage the NDA: @$1
Rapidly triage incoming NDAs against standard screening criteria. Classify the NDA for routing: standard approval, counsel review, or full legal review.
Important: You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
Invocation
/triage-nda
Workflow
Step 1: Accept the NDA
Accept the NDA in any format:
- File upload: PDF, DOCX, or other document format
- URL: Link to the NDA in a document system
- Pasted text: NDA text pasted directly
If no NDA is provided, prompt the user to supply one.
Step 2: Load NDA Playbook
Look for NDA screening criteria in local settings (e.g., legal.local.md).
The NDA playbook should define:
- Mutual vs. unilateral requirements
- Acceptable term lengths
- Required carveouts
- Prohibited provisions
- Organization-specific requirements
If no NDA playbook is configured:
- Proceed with reasonable market-standard defaults
- Note clearly that defaults are being used
- Defaults applied:
- Mutual obligations required (unless the organization is only disclosing)
- Term: 2-3 years standard, up to 5 years for trade secrets
- Standard carveouts required: independently developed, publicly available, rightfully received from third party, required by law
- No non-solicitation or non-compete provisions
- No residuals clause (or narrowly scoped if present)
- Governing law in a reasonable commercial jurisdiction
Step 3: Quick Screen
Evaluate the NDA against each screening criterion systematically.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 265 lines · 118 tokens per session scan A 80fbee6dc370
triage-nda-th is a skill published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 7mo ago), licensed MIT. It adds 118 tokens to every session and 3,211 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to triage-nda, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…