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 arunbalajiraju-proc/procurement-ai-assistant --skill sla-review-skillgit clone --depth 1 https://github.com/arunbalajiraju-proc/procurement-ai-assistantWrote 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/arunbalajiraju-proc/procurement-ai-assistant/sla-review-skill)<a href="https://agentmods.dev/skills/arunbalajiraju-proc/procurement-ai-assistant/sla-review-skill"><img src="https://agentmods.dev/badge/skills/arunbalajiraju-proc/procurement-ai-assistant/sla-review-skill/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/arunbalajiraju-proc/procurement-ai-assistant/sla-review-skill"><img src="https://agentmods.dev/badge/skills/arunbalajiraju-proc/procurement-ai-assistant/sla-review-skill.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.00036 | $0.02892 |
| Opus 5 | $0.00018 | $0.01446 |
| Sonnet 5 | $0.00007 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
sla-review-skill 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.
How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Name
Procurement SLA Review Skill
Purpose
This skill helps AI support procurement professionals with structured review of service levels, KPIs, performance requirements, service credits, reporting obligations, escalation processes, and supplier performance management language.
Use this skill when reviewing or drafting SLA/KPI content for an RFP, contract, SOW, supplier proposal, vendor performance framework, or QBR preparation.
This skill should not create generic SLA language. It should help determine whether each SLA is measurable, reportable, enforceable, commercially appropriate, and aligned to business criticality.
This skill does not finalize legal remedies, approve penalties, set operational targets without business-owner validation, or replace procurement, legal, finance, technical, or business-owner review.
Composability
This skill is standalone. If other Procurement AI Assistant skills are installed, the AI may combine relevant skills for a multi-step procurement request. Do not assume another skill is available; preserve this skill's own guardrails and human review points.
Core Principle
A weak SLA often looks fine until something goes wrong.
The AI should not only ask whether an SLA exists.
It should ask whether the SLA can actually be managed after award.
Every SLA should pass five tests:
Metric -> Measurement -> Reporting -> Remedy -> Escalation
If one of these is missing, the SLA may be difficult to manage, enforce, or use in supplier performance discussions.
When to Use
Use this skill when the user needs help with:
- SLA review
- KPI review
- Service level drafting
- Performance requirement drafting
- RFP/RFB/RFQ/SOW SLA sections
- Contract SLA schedules
- Supplier proposal review
- Vendor performance management framework
- Service credit review
- Reporting obligation review
- Escalation process review
- QBR preparation
- Supplier performance issue analysis
- SLA gap analysis
- Business-owner SLA validation questions
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.
- 12d ago First seen · 479 lines · 36 tokens per session scan A ee8c84096424
sla-review-skill is a skill published in the GitHub repository arunbalajiraju-proc/procurement-ai-assistant (13 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,892 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.
Other skills, from other repositories
standards-expert
Expert-level ISO standards, quality management, compliance, and certification. Use when the user mentions ISO standards, quality management, compliance, or certification, or when the task involves Compliance & Certification, Auditing, or Continuous Improvement.
vendor-evaluation
Build vs Buy scorecard, vendor lock-in risk, SLA negotiation and vendor management.
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.…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…