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 agntcy/dir-mcp --skill create-oasf-recordgit clone --depth 1 https://github.com/agntcy/dir-mcpWrote 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/agntcy/dir-mcp/create-oasf-record)<a href="https://agentmods.dev/skills/agntcy/dir-mcp/create-oasf-record"><img src="https://agentmods.dev/badge/skills/agntcy/dir-mcp/create-oasf-record.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.00031 | $0.00669 |
| Opus 5 | $0.00015 | $0.00334 |
| Sonnet 5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
create-oasf-record 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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create OASF Agent Record
Use this skill to register an AI agent or MCP server in the AGNTCY Agent Directory by generating a valid OASF record.
Record structure
An OASF record is a JSON document describing an AI agent or MCP server. Required top-level fields:
name— URL-based identifier, e.g."https://github.com/example/my-agent"version— semver string, e.g."v1.0.0"description— human-readable summaryskills— array of OASF skill objects ({ "id": "...", "name": "..." })locators— array of deployment locators (Docker image, PyPI, npm, etc.)
Workflow
1. Generate the record
Use the create_record prompt to analyze the current codebase and produce a draft OASF record:
/create_record
The prompt inspects the repo structure, README, and code to infer:
- Agent name, version, and description
- Applicable skills and domains from the OASF taxonomy
- Locators (Docker image, package URL, etc.)
- Authors and license
Optionally specify an output path:
/create_record output_path=agent.json
2. Explore the skill taxonomy (optional)
If the generated skills look off, browse the OASF taxonomy to find better matches:
Call agntcy_oasf_get_schema_skills with version="1.0.0"
Then drill into a category:
Call agntcy_oasf_get_schema_skills with version="1.0.0", parent_skill="Software Development"
Use the returned id values in the record's skills array.
3. Validate the record
Validate the JSON before publishing:
Call agntcy_oasf_validate_record with record_json=<the record JSON string>
Fix any validation_errors reported. Common issues:
- Missing required fields (
name,version,description) - Invalid skill or domain IDs (use the taxonomy tools to find correct IDs)
- Malformed locators
4. Publish to the Directory
Once the record is valid, push it:
Call agntcy_dir_push_record with record_json=<the validated record JSON>
Save the returned cid — it is the content-addressable identifier for this record version and the canonical reference for it; there is no other way to retrieve the exact same record later without re-pushing.
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.
- 4d ago Changed · +9 lines 6a13351a54d0
- 8d ago First seen · 74 lines · 31 tokens per session scan A 12b75c2f60f0
create-oasf-record is a skill published in the GitHub repository agntcy/dir-mcp (2 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 669 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…