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/overviewgit 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.00030 | $0.01412 |
| Opus 5 | $0.00015 | $0.00706 |
| Sonnet 5 | $0.00006 | $0.00282 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
overview scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `/api/docs/*` | scripts, `curl`, anything without MCP | the same tools as plain GET | How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serving agents
People can read this site. Agents can call it. These are different jobs, so the site serves them through different surfaces.
| Surface | Who uses it | What it is |
|---|---|---|
llms.txt, llms-full.txt |
crawlers, training pipelines | a map of the corpus and the corpus itself, as text |
<page>.md, Accept: text/markdown |
anything that follows a link | every page as clean Markdown |
/mcp |
Claude, Cursor, ChatGPT, Claude Code | the docs as callable tools |
/api/docs/* |
scripts, curl, anything without MCP |
the same tools as plain GET |
| WebMCP | agents running inside the visitor's browser | the same tools again, registered on the page |
/agent-manifest.json |
the Worker, and anyone curious | the outline of every page with line offsets |
The first two rows are static. They exist in the build output and cost
nothing to serve. The Worker serves the rest, and agents.enabled in
src/docs.config.ts
turns them all on together.
The four tools
worker/agent/tools.ts defines each tool once, as a
name, a description, a JSON Schema and a handler. MCP, HTTP and WebMCP are
three adapters over that one array. This is why they always agree on what
search means. Adding a new tool takes one entry.
search(query, limit?)
Returns passages grouped by the page they came from.
{
"query": "custom domain",
"pages": [
{
"url": "https://docs.example.com/guides/deployment",
"title": "Deploy your site",
"description": "…",
"type": "page",
"tab": "Guides",
"updated": "2026-08-03",
"totalLines": 176,
"chunks": [
{ "lines": [52, 74], "heading": "Host configuration", "text": "…" },
{ "lines": [75, 97], "heading": "Host configuration › Caching", "text": "…" }
]
}
]
}
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 · 133 lines · 30 tokens per session scan A 2eb9adf3731e
overview is an agent published in the GitHub repository DuvInc/duvlify (23 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 1,412 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.