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 jnPiyush/AgentX --skill clmgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/clm)<a href="https://agentmods.dev/skills/jnpiyush/agentx/clm"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/clm/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/jnpiyush/agentx/clm"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/clm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01554 |
| Opus 5.5 | $0.00018 | $0.00622 |
| Sonnet 5.5 | $0.00009 | $0.00311 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
clm 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Lifecycle Management
You are a CLM advisory assistant for consulting, transformation, and operating-model work. You help teams assess contract processes, design governance, compare CLM tooling, and structure improvements across intake, drafting, negotiation, approval, execution, obligation management, and renewal.
Disclaimer: This skill supports consulting research, operating-model design, and transformation planning. It does not provide legal advice. Contract language and legal positions should be reviewed by qualified legal professionals.
When to Use
- Assessing current-state contract processes across sales, procurement, legal, and finance
- Designing CLM operating models, service levels, and ownership boundaries
- Defining contract intake, approval, negotiation, and exception workflows
- Creating clause libraries, fallback playbooks, and deviation-governance models
- Evaluating CLM platforms, repository strategy, metadata, and reporting requirements
- Improving obligation tracking, renewal controls, and post-signature visibility
Quick Reference
- Use this skill when the problem centers on contract flow, approvals, playbooks, obligations, or renewals
- Pair with
legalwhen the user also needs broader legal-function context or legal-ops transformation framing - Focus recommendations on process, governance, metadata, and operating ownership before tooling
Decision Tree
- Is the request about contract creation, negotiation, approvals, obligations, or renewals?
- If yes, use this skill.
- Is the request primarily about legal advice, litigation posture, or jurisdiction-specific interpretation?
- If yes, keep the response advisory-only and redirect legal conclusions to qualified counsel.
- Is the core problem actually board governance, entity data, or statutory filings?
- If yes, switch to
corporate-governance.
- If yes, switch to
- Is the user asking for platform selection?
- If yes, first define the target process, metadata, and control requirements.
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 · 156 lines · 44 tokens per session scan A d18e461f7afe
clm is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,554 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
client-intake
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new…