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 spend-analysis-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/spend-analysis-skill)<a href="https://agentmods.dev/skills/arunbalajiraju-proc/procurement-ai-assistant/spend-analysis-skill"><img src="https://agentmods.dev/badge/skills/arunbalajiraju-proc/procurement-ai-assistant/spend-analysis-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/spend-analysis-skill"><img src="https://agentmods.dev/badge/skills/arunbalajiraju-proc/procurement-ai-assistant/spend-analysis-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.00032 | $0.03156 |
| Opus 5 | $0.00016 | $0.01578 |
| Sonnet 5 | $0.00006 | $0.00631 |
| Haiku 4.5 | $0.00003 | $0.00316 |
Grade A, and why
spend-analysis-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 — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Name
Procurement Spend Analysis Skill
Purpose
This skill helps AI support procurement spend analysis through a structured, repeatable workflow.
Use this skill when a procurement professional needs to clean, classify, group, compare, and challenge spend data to identify patterns, anomalies, contract gaps, renewal risks, supplier concentration, overlapping products or services, and potential sourcing opportunities.
This skill should not simply summarize totals. It should help procurement understand where spend is going, what may require investigation, and where a human should validate a potential opportunity.
This skill does not automatically classify every overlap as waste, calculate final savings without evidence, recommend supplier termination, or replace procurement, finance, business-owner, legal, security, or technical 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
Spend analysis is not only about totals.
It is about finding patterns that deserve procurement attention.
The AI should follow this workflow:
Inspect -> Clean -> Normalize -> Classify -> Group -> Compare -> Challenge -> Validate -> Prioritize
The goal is to move from a raw spend file to a procurement-ready opportunity and risk view.
When to Use
Use this skill when the user needs help with:
- Spend data cleaning
- Supplier normalization
- Category classification
- Spend cube preparation
- Tail-spend analysis
- Supplier concentration analysis
- Duplicate or overlapping supplier review
- SaaS and software spend analysis
- Licence and usage review
- Contract coverage analysis
- Renewal pipeline review
- Maverick or off-contract spend review
- Invoice and purchase-order anomaly detection
- Category opportunity identification
- Supplier consolidation analysis
- Savings-opportunity preparation
- Executive spend summaries
- Procurement pipeline development
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 · 542 lines · 32 tokens per session scan A 2619aa564b76
spend-analysis-skill is a skill published in the GitHub repository arunbalajiraju-proc/procurement-ai-assistant (13 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 3,156 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
procurement
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you…
trading-expert
Expert-level algorithmic trading, market systems, quantitative analysis, and trading platforms. Use when the user mentions algorithmic trading, quant, markets, finance, or high-frequency trading, or when the task involves Trading Systems, Market Data, or Execution.
insurance-expert
Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions. Use when the user mentions underwriting, claims, actuarial, risk, or insurtech, or when the task involves Insurance Systems, Insurance Types, Standards and Regulations, or Claims Processing.
accountant-expert
Expert-level accounting, tax, financial reporting, and accounting systems. Use when the user mentions accounting, tax, financial reporting, GAAP, or IFRS, or when the task involves Accounting Principles, Financial Statements, Tax & Compliance, or Accounting Systems.
finops-expert
Expert-level cloud financial operations, cost optimization, and cloud economics. Use when the user mentions cloud cost, optimization, cloud economics, or AWS cost, or when the task involves FinOps Fundamentals, Cost Management, FinOps Practices, or Cost Visibility.
banking-expert
Expert-level banking systems, core banking, regulations, and banking technology. Use when the user mentions finance, core banking, regulations, or payments, or when the task involves Banking Systems or Key Technologies.