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 sparq-org/sparq --skill rdf-wrappergit clone --depth 1 https://github.com/sparq-org/sparqWrote 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/sparq-org/sparq/rdf-wrapper)<a href="https://agentmods.dev/skills/sparq-org/sparq/rdf-wrapper"><img src="https://agentmods.dev/badge/skills/sparq-org/sparq/rdf-wrapper/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/sparq-org/sparq/rdf-wrapper"><img src="https://agentmods.dev/badge/skills/sparq-org/sparq/rdf-wrapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 90 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00130 | $0.05579 |
| Opus 5.5 | $0.00052 | $0.02232 |
| Sonnet 5.5 | $0.00026 | $0.01116 |
| Haiku 4.5 | $0.00013 | $0.00558 |
Grade A, and why
rdf-wrapper 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 18d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use sparq-wrapper
Add the opt-in crate explicitly. It is publish = false (not on crates.io), so
take it and sparq-core from the same git source to share one Graph type:
[dependencies]
sparq-core = { git = "https://github.com/sparq-org/sparq" }
sparq-wrapper = { git = "https://github.com/sparq-org/sparq" }
oxrdf = "0.3"
Load a graph, borrow it, and traverse with typed predicates:
use oxrdf::NamedNode;
use sparq_core::Graph;
use sparq_wrapper::Store;
let graph = Graph::load_str(
"@prefix ex: <http://example.org/> . ex:alice ex:knows ex:bob . ex:bob ex:age 42 .",
"turtle",
)?;
let store = Store::borrowed(&graph);
let alice = NamedNode::new("http://example.org/alice")?;
let knows = NamedNode::new("http://example.org/knows")?;
let age = NamedNode::new("http://example.org/age")?;
let bob = store.node(alice).out(&knows).next().expect("friend");
assert_eq!(bob.out(&age).next().expect("age").as_i64()?, 42);
# Ok::<(), Box<dyn std::error::Error>>(())
.out() and .r#in() return NodeSet, an ExactSizeIterator<Item = Node>;
the raw identifier is Rust's required spelling for a method named in.
Call .values() on a traversal to yield owned oxrdf::Terms. An absent focus
or predicate is valid and yields an empty iterator. Node::dataset() exposes a
borrowed dataset wrapper; .graph() is the raw sparq_core::Graph escape hatch.
Choose ownership deliberately:
Store::borrowed(&graph)is read-only and tied to the graph's lifetime.Store::owned(graph)andStore::new()own the graph and allowinsert/remove. Nodes borrow the store, so stop using them before a write and reacquire them afterwards.- Traversal addresses the default graph in M1. Reach named graphs through the
opt-in
proposed-graph-scopeGraphScope(below) or the raw graph.
Typed accessors are strict:
as_str()acceptsxsd:stringandrdf:langString.as_i64()accepts the XML Schema integer family, enforces every derived datatype's exact bounds (bytethroughunsignedLong), then checks that the value is representable asi64.as_bool()accepts onlyxsd:boolean, includingtrue/false/1/0.as_typed_literal()returns lexical form, datatype, and language.
All return Result<_, AccessError>; do not silently coerce a mismatched RDF
datatype.
Eleven explicitly experimental, default-off features track proposals that remain unlanded in rdfjs/wrapper:
sparq-wrapper = { git = "https://github.com/sparq-org/sparq", features = [
"proposed-async-events",
"proposed-async-node",
"proposed-async-store",
"proposed-cardinality",
"proposed-codecs",
"proposed-distinct",
"proposed-graph-scope",
"proposed-graph-scope-events",
"proposed-json",
"proposed-observe",
"proposed-typed-focus",
] }
Every proposal feature is implemented. proposed-distinct is exposed as
inherent Dataset methods in the crate root rather than through a proposed::
module. The async node and async events features imply proposed-async-store;
graph-scope events implies proposed-graph-scope; the event features reuse
proposed-observe's ChangeEvent / SubscriptionId. See the
per-feature proposal status pages for the feature
inventory.
proposed-async-store adds sparq_wrapper::proposed::async_store — the
wrapper shape over a store whose reads are not synchronous (an HTTP endpoint, a
Solid pod, an out-of-core on-disk index), based on rdfjs/wrapper
issue #10 and
draft PR #97. Implement
AsyncStoreBackend for the backend, then use AsyncStore exactly like Store.
AsyncNode::out / AsyncNode::r#in return a NodeStream that wraps each term
into an AsyncNode as it arrives: the first node is observable before the
backend finishes producing, and there is deliberately no collect. Building a
stream polls nothing; dropping one drops the backend stream, so the wrapper
never polls or drains it again. NodeStream::next is cancellation-safe — the
wrapper buffers nothing of its own.
What ships with it
12 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.
- references/async_events.md 717 B
- references/async_node.md 694 B
- references/async_store.md 823 B
- references/cardinality.md 138 B
- references/codecs.md 122 B
- references/distinct.md 293 B
- references/graph_scope_events.md 775 B
- references/graph_scope.md 138 B
- references/json.md 891 B
- references/observe.md 130 B
- references/README.md 399 B
- references/typed_focus.md 138 B
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.
- 18d ago Changed · +2 lines 12e96053fe36
- 21d ago Changed · +83 lines · +14 tokens per session e532ebdacb3a
- 1mo ago First seen · 372 lines · 116 tokens per session scan A f2fa21b72455
rdf-wrapper is a skill published in the GitHub repository sparq-org/sparq (13 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 5,579 once invoked, about $0.0005 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
azure-cosmos-rust
Azure Cosmos DB library for Rust (NoSQL API). Document CRUD, containers, and globally distributed data. Triggers: "cosmos db rust", "CosmosClient rust", "document crud rust", "NoSQL rust", "partition key rust".
azure-cosmos-rust
Client library for Azure Cosmos DB NoSQL API — globally distributed, multi-model database.
surrealism
SurrealDB Surrealism WASM extension development. Write Rust functions, compile to WASM, deploy as database modules. Part of the surreal-skills collection.
golem-add-sqlite-rust
Use embedded SQLite from a Rust Golem agent with rusqlite and the WASI VFS. Use for local SQL state, file-backed SQLite, or an agent-owned embedded database.
golem-add-turso-rust
Use the Turso Rust crate for an in-memory embedded SQL database in a Rust Golem agent. Use when asking for Turso, local Turso SQL, or the proven WASI-compatible Turso configuration.
golem-add-ignite-rust
Using golem:rdbms/ignite2 from a Rust Golem agent. Use when the user asks to connect to Apache Ignite 2, run SQL over Ignite, or use Ignite from Rust agent code.