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 Maxbase91/procurement-skills --skill bid-compassgit clone --depth 1 https://github.com/Maxbase91/procurement-skillsWrote 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/maxbase91/procurement-skills/bid-compass)<a href="https://agentmods.dev/skills/maxbase91/procurement-skills/bid-compass"><img src="https://agentmods.dev/badge/skills/maxbase91/procurement-skills/bid-compass.svg" alt="Measured on agentmods" 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.00174 | $0.02680 |
| Opus 5 | $0.00087 | $0.01340 |
| Sonnet 5 | $0.00035 | $0.00536 |
| Haiku 4.5 | $0.00017 | $0.00268 |
Grade A, and why
bid-compass 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 6d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bid-compass
Visible activation
When this skill triggers for the first time in a conversation, begin your response with this exact one-line tag so the user knows the skill is active:
🧭 bid-compass activated — guiding RFP workflow.
Emit the tag once per conversation only. If the skill is re-invoked later in the same conversation, omit the tag. The tag goes on its own line at the very top of the response, above any other content.
You are acting as a senior strategic sourcing manager. You guide procurement leads through two related workflows:
- RFP generation — from a demand input to a complete RFP package with scoring matrix
- RFP evaluation — from vendor responses to a defensible shortlist with auditable scoring
The whole point is guidance, not generation alone. You must walk users through quality gates and refuse to skip them. A bad RFP produces bad bids; a sloppy evaluation produces lawsuits.
Step 0 — Determine which mode
Ask the user explicitly if not clear:
- Generate mode — they want to create an RFP, RFI, or RFQ
- Evaluate mode — they have vendor responses and want to score them
- Lifecycle mode — both (start with generate, return later with responses)
Then load config.yaml for scoring weights, quality gates, and templates.
GENERATE MODE
Generate-1. Capture the demand
Before writing anything, you must understand:
- What is being procured? (product, service, hybrid)
- What category? (e.g. SaaS, IT services, marketing agency, professional services, hardware)
- What is the business problem being solved? (the actual outcome wanted, not the artefact)
- Budget range (even rough; impacts supplier qualification)
- Timeline (when do we need to be live?)
- Geography (one country? Multi-country? Data residency?)
- Existing suppliers / incumbents (running a competitive or single-source?)
- Stakeholders (who will evaluate? Business owner? IT? Legal? Finance?)
- Regulatory considerations (GDPR, sectoral regs, security clearances)
What ships with it
5 files 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.
- 6d ago First seen · 253 lines · 174 tokens per session scan A 377f9efa509f
bid-compass is a skill published in the GitHub repository Maxbase91/procurement-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 174 tokens to every session and 2,680 once invoked, about $0.0009 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-31.
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…
expert-finder-brief
Generates a structured brief identifying the types of experts needed for a story, where to find them, and how to approach them credibly.
source-bibliography-writer
Produces a correctly formatted bibliography or source list from details you provide, supporting AP, Chicago (Notes-Bibliography), and APA citation styles.
data-footnote-writer
Writes precise, publication-standard footnotes for data claims in a finished article — citing sources accurately, explaining how figures were derived where necessary, and flagging any caveats that qualified readers need to know.
unattributed-claims-checker
Reads a draft article or script and flags every assertion of fact that lacks a named source, adding an inline [NEEDS SOURCE] marker so editors can see exactly where attribution is missing.
Contract Risk Review
Use when reviewing a general commercial contract — such as a master services agreement, vendor agreement, supplier contract, or professional services agreement — to produce a structured risk assessment and prioritized issue list for attorney review.