Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/openlinksoftware/ai-agent-skills/resource-access-offers-generator)<a href="https://agentmods.dev/skills/openlinksoftware/ai-agent-skills/resource-access-offers-generator"><img src="https://agentmods.dev/badge/skills/openlinksoftware/ai-agent-skills/resource-access-offers-generator/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/openlinksoftware/ai-agent-skills/resource-access-offers-generator"><img src="https://agentmods.dev/badge/skills/openlinksoftware/ai-agent-skills/resource-access-offers-generator.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.00079 | $0.08579 |
| Opus 5 | $0.00039 | $0.04290 |
| Sonnet 5 | $0.00016 | $0.01716 |
| Haiku 4.5 | $0.00008 | $0.00858 |
Grade A, and why
resource-access-offers-generator 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 yesterday.
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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Access Offers Generator
Generate valid RDF Turtle documents containing File Access, Graph Access, API Access, or Chat Service offers.
Minimum Input Requirements
| Input | Required | Example |
|---|---|---|
| License resource IRI | Yes (not for Chat Service — see its own section) | URL of protected file/graph |
| Price | Yes | 2.99 |
| Description | Yes | Free text — name/prefLabel/comment auto-derived |
| Host platform | No (default: URIBurner) | linkeddata.uriburner.com |
Host Platform Profiles
URIBurner (linkeddata.uriburner.com), ODS-QA (ods-qa.openlinksw.com), Localhost (localhost)
Workflow
- Elicit offer type (file/graph/api/chatservice), host, license IRI, price, description
- Derive name, prefLabel, comment from description
- Load prompt template from
prompts/ - Substitute placeholders, generate Turtle
- Validate syntax (rdflib), validate SHACL (
scripts/validate-offers-shacl.py) - Run Post-Generation Checklist, save to
/Users/jacqui/source/ttl/my_git_forks/virtuoso-82-offers-description/(default output directory for all generated offer files), provide loading instructions
Document Metadata Block (source:)
Immediately after the @prefix declarations, every generated file MUST open with a schema:CreativeWork block describing the Turtle file being generated itself — never the licensed resource (file/graph/API being sold). Declare:
@prefix source: <http://virtuoso.openlinksw.com/data/turtle/{output-filename}> .
@prefix : <#> .
source: a schema:CreativeWork ;
schema:name "{Document title}" ;
schema:description "{What this document's offers cover}" ;
schema:author <http://www.openlinksw.com/#this> ;
cc:attributionName "OpenLink Software" ;
schema:datePublished "{dateTime}"^^xsd:dateTime ;
schema:dateModified "{dateTime}"^^xsd:dateTime .
{output-filename} is the actual filename this Turtle file will be saved as (matching the convention in the two prior art files: http://virtuoso.openlinksw.com/data/turtle/FileAccessOffers-License-Prices.ttl, http://virtuoso.openlinksw.com/data/turtle/OPALOffers-Licenses-Prices-ods-qa-SPARQL-API.ttl) — this host/path is fixed regardless of which host platform profile the licensed resource lives on.
Every generated Offer, License, and PriceSpecification node MUST carry wdrs:describedby source: pointing at this document node — that relation is what "identifies" the document as their source. The licensed resource itself is never separately described as a schema:CreativeWork — it's referenced only via opllic:uriParameter/opllic:graphParameter. The SHACL gate enforces wdrs:describedby (sh:class schema:CreativeWork) as required on Offer, License, and PriceSpecification shapes, and DocumentShape requires schema:name/schema:author/schema:datePublished/schema:dateModified on whatever node that resolves to.
What ships with it
13 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.
- prompts/api-access-offer-prompt.md 0 B
- prompts/file-access-offer-prompt.md 0 B
- prompts/graph-access-offer-prompt.md 0 B
- references/loading-instructions.md 438 B
- references/offer-iri-patterns.md 2.9 KB
- references/offer-shapes-reference.md 2.8 KB
- references/prefixes.ttl 627 B
- scripts/validate-offers-shacl.py 2.5 KB runs code
- shacl/api-access-offer-shape.ttl 6.3 KB
- shacl/chat-service-offer-shape.ttl 3.3 KB
- shacl/common-offer-shape.ttl 4.4 KB
- shacl/file-access-offer-shape.ttl 2.5 KB
- shacl/graph-access-offer-shape.ttl 4.5 KB
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.
- yesterday Changed · +1 lines 4149f3d37588
- 10d ago First seen · 269 lines · 79 tokens per session scan A 3f977aed65ce
resource-access-offers-generator is a skill published in the GitHub repository OpenLinkSoftware/ai-agent-skills (38 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 8,579 once invoked, about $0.0004 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-30.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…