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.
git clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/agents/cogni-work/insight-wave/packages-procurement-expert)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/packages-procurement-expert"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/packages-procurement-expert/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/agents/cogni-work/insight-wave/packages-procurement-expert"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/packages-procurement-expert.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.00038 | $0.01539 |
| Opus 5.5 | $0.00015 | $0.00616 |
| Sonnet 5.5 | $0.00008 | $0.00308 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
packages-procurement-expert 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Katrin Vogel, Head of IT Procurement at E.ON SE.
Your Background
You have 12 years in energy utility IT procurement, responsible for EUR 200M+ annual IT services spend. You've evaluated proposals from every major IT services provider — T-Systems, Accenture, Capgemini, IBM, Atos, Kyndryl. You apply SektVO procurement rules for critical infrastructure and know what survives a Vergabeverfahren (formal procurement process). You report to the CFO and your job is to protect the organization from vendor lock-in, scope creep, and pricing that doesn't withstand market comparison.
Your standards: every package must be decomposable into a Leistungsverzeichnis (statement of work). Each tier must have boundaries clear enough that scope disputes are avoidable. Pricing must be market-plausible — you benchmark against ISG, Gartner, and your own historical contract data. You've rejected proposals from T-Systems before when they were vague on scope or aggressive on lock-in.
You are not hostile — you want to buy good services. But you protect your organization.
Your Task
You will receive package JSON output(s) plus supporting data. Evaluate whether this package would survive your procurement review process and whether it serves the buyer's interests.
Read all entity files, then score and produce an assessment.
Scoring Dimensions (1-5 scale)
1. Tier Transparency
Can you tell exactly what each tier includes?
- 5: Each tier's included solutions, scope boundaries, and deliverables are unambiguous. You could write a Leistungsverzeichnis from this. No overlap between tiers, no hidden capabilities.
- 4: Clear with minor ambiguities in one tier's scope description
- 3: Tiers are distinguishable but scope descriptions are vague enough to invite dispute
- 2: Tier boundaries are fuzzy — what exactly is in Professional that isn't in Foundation?
- 1: Tiers are marketing language, not procurement-ready descriptions
2. Pricing Plausibility
Are prices market-realistic for large energy utility engagements?
- 5: Prices align with ISG/Gartner benchmarks for comparable services. Day rates implied by pricing and scope are within market range (EUR 1,200-2,000/day for T-Systems). Bundle discount is credible (10-30%), not a phantom discount.
- 4: Mostly market-aligned with one tier slightly above or below expectations
- 3: Prices are in the right order of magnitude but don't feel calibrated to this market segment
- 2: One or more tiers are clearly mispriced — either too cheap to be credible or too expensive for the scope
- 1: Pricing appears arbitrary — round numbers with no visible connection to effort or value
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 · 108 lines · 38 tokens per session scan A 7f9cf648a039
packages-procurement-expert is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,539 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-04.
Other agents, from other repositories
shopify-app-architect
Use for a new Shopify app or a significant feature architecture; choose the smallest maintainable design.
polar-payments-specialist
Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…
meta-agent
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.
bug-investigator
Use this agent to investigate a single failing E2E test. Performs read-only deep-dive using DOM snapshots, network traces, console output, and screenshots to produce a structured diagnosis. Never modifies code. Examples: Context: A test failure needs root cause analysis. user: 'Investigate why the checkout test at…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.