purchase-request

purchase-request is a skill for Claude Code, Codex from microsoft/aibast-agents-library. It costs 18 tokens per session (864 once invoked), scanned A, original, MIT.

A procedure for reviewing a purchase request against its context and approval level. It uses uploaded synthetic records and rules.

In plain words
What is it for?
Use it to prepare a review brief for purchase request PR-5001, a fictional $125,000 request requiring CFO review.
Why use it?
It helps clarify what the request supports, what remains uncertain, and who must review it before action. It prevents a draft review from being mistaken for an approval or completed purchase.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a review brief for purchase request PR-5001, a fictional $125,000 request requiring CFO review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/aibast-agents-library/aibast_purchase-request_01
About the project

AIBAST Agents Library is a collection of industry-focused AI agent templates accompanied by a local server that connects agents to GitHub Copilot for language-model inference. It helps developers create and run tool-using agents and isolated project environments, with an optional cloud-backed path for persistent memory. The catalogue entries provide the repository's agents, skills, commands, hooks, and instructions.

microsoft/aibast-agents-library · 8 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/aibast-agents-library --skill aibast_purchase-request_01
Clone the repo
git clone --depth 1 https://github.com/microsoft/aibast-agents-library

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for purchase-request

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/aibast_purchase-request_01/github.svg)](https://agentmods.dev/skills/microsoft/aibast-agents-library/aibast_purchase-request_01)
Your own site
<a href="https://agentmods.dev/skills/microsoft/aibast-agents-library/aibast_purchase-request_01"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/aibast_purchase-request_01/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.

agentmods 80×15 button for purchase-request

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/aibast-agents-library/aibast_purchase-request_01"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/aibast_purchase-request_01.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00864
Opus 5.5 $0.00007 $0.00346
Sonnet 5.5 $0.00004 $0.00173
Haiku 4.5 $0.00002 $0.00086

Measured 1mo ago against content hash 6283b80fc92f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

purchase-request 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.

solutions/procurement-agent/manual/skills/aibast_purchase-request_01/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purchase-request review

Use when a procurement manager asks for request context and the applicable approval level.

Procedure

  1. Use this uploaded purchase-request skill with aibast_procurement-agent-synthetic-records.md and aibast_procurement-agent-rules-and-guardrails.md. Retrieve and cite both. The default cloud-upgrade record is PR-5001; do not substitute it for a different explicitly requested but missing record.
  2. Read the request fields and quote its source-recorded justification without treating it as independently verified. Read the category snapshot and approval thresholds; keep their values unchanged.
  3. Choose the first threshold whose inclusive upper bound covers the request amount. Retain its cap and the Unlimited / CEO + Board tier. Do not invent dollar-only lower bounds or serial approval chains. The SLA is a source label, not evidence that a review clock or approval started. It is not a promise of approval. Do not invent an approver for unspecified spend.
  4. The snapshot has no request-to-commitment mapping. Finance reconciliation must establish whether a request is already included in commitments. Do not infer inclusion from matching amounts or request status. Do not calculate hypothetical revised balances or utilization, or assert incremental budget effects without that mapping. Do not present a request-to-availability ratio as incremental consumption.
  5. Preserve existing budget exceptions. Technology is already At Risk; report its recorded utilization and availability, not an unbreached starting condition or a revised balance. Identify the unresolved human reviews in the common rules, including Finance reconciliation, before any human action.

Required response contract

Use these headings in order, with exact wording and capitalization. Populate each section from the retrieved source; never output unfilled placeholders. For PR-5001, the title is exactly Purchase Request Review: PR-5001.

Read the full file on GitHub · 88 lines

Changes

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.

  1. 1mo ago Changed · +62 lines 6283b80fc92f
  2. 1mo ago First seen · 26 lines · 18 tokens per session scan A 3db2c5345c11

Subscribe to this mod's changes

purchase-request is a skill published in the GitHub repository microsoft/aibast-agents-library (8 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 864 once invoked, about $0.0001 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.