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 agentmods add agents/duvinc/duvlify/discoverygit clone --depth 1 https://github.com/DuvInc/duvlifyWhat 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 | $0.00031 | $0.02154 |
| Opus 5 | $0.00015 | $0.01077 |
| Sonnet 5 | $0.00006 | $0.00431 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
discovery 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 2d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discoverability
An endpoint that no agent ever finds is dead code. The build advertises each
endpoint in the places agents actually look: the ## Optional section of
llms.txt, a comment block in robots.txt, and Link headers on every
page.
/.well-known/api-catalog
The Worker serves two more well-known URIs, both defined relative to the
origin: /.well-known/mcp.json (with the server-card spelling beside it) and
/.well-known/api-catalog.
The catalog follows RFC 9727, a
specification that answers a question the documentation itself cannot:
which API. A site that documents a product actually has two APIs: the
product's own API, and this documentation's own read-only API under
/api/docs. Until an agent reads the docs, it has no way to tell the two
apart. The catalog states the difference in one fetch:
{
"linkset": [
{ "anchor": "https://api.example.com/v1",
"service-desc": [{ "href": "https://docs.example.com/openapi.json", "type": "application/openapi+json" }],
"service-doc": [{ "href": "https://docs.example.com/", "type": "text/html" }] },
{ "anchor": "https://docs.example.com/api/docs",
"service-desc": [{ "href": "https://docs.example.com/api/docs/openapi.json", "type": "application/openapi+json" }],
"service-doc": [{ "href": "https://docs.example.com/", "type": "text/html" }],
"status": [{ "href": "https://docs.example.com/api/docs", "type": "application/json" }] }
]
}
Three details matter, and test/agents.test.mjs asserts each one rather
than leaving it to review:
- The media type is
application/linkset+json(RFC 9264), notapplication/json. A client negotiating for a linkset will not accept the generic type. - Every relation's value is an array of link target objects, even when there is only one link. A bare object is well-formed JSON, but no generic client reads it correctly.
- The first entry is anchored on the API's own base URL, taken from the
specification's
servers[0].url, not on the page that describes it. This lets an agent holding a request URL match it against the catalog.
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.
- 2d ago First seen · 177 lines · 31 tokens per session scan A 8d52e419d0b1
discovery is an agent published in the GitHub repository DuvInc/duvlify (23 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 2,154 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-30.
Other agents, from other repositories
mcp-connection
Connect Claude Code or any MCP-compatible agent to your Projektor instance.
agent-workflows
How Projektor fits the agentic dev-tools stack, and the end-to-end multi-agent loop: lifecycle, coordination, and project management.
enhance-core-tools
Enhance core search, operators, and workflow tools with new capabilities.
implement-experimental
Implement MCP tools for experimental techniques and add experimental operator data.
add-tools-agent
Create new MCP tool endpoints to extend the TouchDesigner MCP server.
workflow-spec
The canonical agent workflow rules: definition of ready, state machine, human gates, WIP limits.