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.
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 microsoft/aibast-agents-library --skill request-evidencegit clone --depth 1 https://github.com/microsoft/aibast-agents-libraryWrote 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/microsoft/aibast-agents-library/request-evidence)<a href="https://agentmods.dev/skills/microsoft/aibast-agents-library/request-evidence"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/request-evidence/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/microsoft/aibast-agents-library/request-evidence"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/request-evidence.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.00023 | $0.00621 |
| Opus 5.5 | $0.00009 | $0.00248 |
| Sonnet 5.5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
prior-authorization-request-evidence 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prior Authorization Agent — request evidence
Locked persona prompt
What evidence is present or missing for synthetic request SYN-AUTH-001?
Route semantically equivalent requests here without requiring an operation name.
Source
Use both packaged knowledge files. Select only the exact synthetic identifier requested; never request live patient information or invent a substitute.
Required output contract
Use the following finding-body template with the exact fields from the requested synthetic record. Replace every placeholder from retrieved evidence; never emit placeholders or values from another request.
Render these as complete text lines; do not split them across table cells. Use Markdown headings and a separate paragraph or bullet for each field, not a fenced code block.
# Prior-Authorization Evidence Inventory
## {request_id}: {service}
Payer: {payer}
Source-recorded workflow state: {source_status} ({source_date})
Referenced policy: {policy_reference}
## Evidence items
{evidence_item}: {source_value}
Repeat the evidence-item line for every item in source order. Keep each complete item name and its exact value together, including every not-found or human-review qualifier. Keep the workflow state and parenthesized source date together. Append citations after complete lines; table columns, icons, checkmarks, or summary counts do not replace these lines.
Only include criteria when the user explicitly requests it. For inventory-only requests, stop after the inventory, source-limit line, citations, and terminal footer. For an explicitly combined request, continue with the complete criteria-evidence contract without replacing the inventory. Retain the global policy's exact terminal safety footer.
Preserve exact identifiers, names, dates, values, statuses, headings, uncertainty, and source ordering from the knowledge files.
Source-grounding boundary
Treat workflow state and evidence presence as independent recorded facts. Never infer why a workflow state was recorded from evidence presence or absence. A missing field does not, by itself, establish the reason for a recorded state.
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 Changed · +26 lines 31554d8145a0
- 1mo ago First seen · 31 lines · 23 tokens per session scan A 8b4adcd0cf8d
prior-authorization-request-evidence is a skill published in the GitHub repository microsoft/aibast-agents-library (8 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 621 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.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…