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 Knuckles-Team/archivebox-api --skill archivebox-api-developmentgit clone --depth 1 https://github.com/Knuckles-Team/archivebox-apiWrote 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/knuckles-team/archivebox-api/archivebox-api-development)<a href="https://agentmods.dev/skills/knuckles-team/archivebox-api/archivebox-api-development"><img src="https://agentmods.dev/badge/skills/knuckles-team/archivebox-api/archivebox-api-development/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/knuckles-team/archivebox-api/archivebox-api-development"><img src="https://agentmods.dev/badge/skills/knuckles-team/archivebox-api/archivebox-api-development.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.00035 | $0.01225 |
| Opus 5.5 | $0.00014 | $0.00490 |
| Sonnet 5.5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
archivebox-api-development 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 today.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchiveBox API Development
This is the repository development skill for archivebox-api. The owning central
delivery row is PIPE-CONNSPEC-R103.4; use this skill with the repository
AGENTS.md, the connector-content and web-source specifications, and the
focused tests.
Repository and runtime map
archivebox_api/mcp_server.pyregisters authentication, core, CLI, KG, and web-source tools. Keep action names and the SDK Connector boundary stable.archivebox_api/api_client.pycomposes the authentication, core, and CLI API wrappers.archivebox_api/auth.pyinjects endpoint credentials and the SDK TLS profile throughget_client; it must not persist secret values.archivebox_api/connector_sources.pyis the live source and schema declaration. Change declarations there rather than duplicating source IDs or mappings in tool code.archivebox_api/web_source.pyimplements the SDK web-source contract: keyless web discovery is separate from ArchiveBox REST authentication, while extractor files use a logged-in Django session and bounded reads.archivebox_api/kg_ingest.pyowns best-effort typed Snapshot, ArchiveResult, Document, Chunk, Tag, and Blob ingestion through the SDK/epistemic-graph boundary. Preserve stable IDs and no-op behavior when the engine is absent.archivebox_api/skills/**,prompts/**,ontology/**, andconnectors/**are package data. A skill change therefore needs a package inclusion check before publication.
Connection and security contract
The REST client uses ARCHIVEBOX_BASE_URL with the ARCHIVEBOX_URL alias.
Bearer/API-key and basic-auth values come from injected ARCHIVEBOX_TOKEN,
ARCHIVEBOX_API_KEY, ARCHIVEBOX_USERNAME, and ARCHIVEBOX_PASSWORD
settings. Keep secrets out of source, skills, fixtures, logs, and test output.
Use the SDK TLS policy selected by ARCHIVEBOX_TLS_PROFILE and
ARCHIVEBOX_TLS_PROFILE_REF; ArchiveSession must keep certificate and
hostname verification governed by the shared resolver. Preserve the supported
stdio, streamable-http, and sse transports, the
MCP_TOOL_MODE surface selection, WEBTOOL/WEB_SOURCETOOL toggles,
and the ARCHIVEBOX_KG_AUTO_INGEST opt-out. Do not add a provider-specific
credential store or a TLS bypass.
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.
- today First seen · 110 lines · 35 tokens per session scan A fc6117e81d0c
archivebox-api-development is a skill published in the GitHub repository Knuckles-Team/archivebox-api (1 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,225 once invoked, about $0.0001 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-10-27.
Other skills, from other repositories
audio-transcriber-development
Develop and maintain the Audio Transcriber connector while preserving its Whisper backend boundary, MCP tool surface, typed transcript ingestion, optional hardware behavior, package resources, and public-first evidence.
jellyfin-kg-ingestion
Natively ingest a Jellyfin library into the epistemic-graph knowledge graph via the jellyfin-mcp MCP server — push library items as typed :MediaAsset/:Book nodes with :hasGenre/:performedBy/:authoredBy links and item overviews as searchable :Document nodes (jellyfiningestlibrary), and item posters as content-addressed…
searxng-kg-ingestion
Persist SearXNG search results into the epistemic-graph knowledge graph via the searxng-mcp MCP server. Use when the agent must turn a web search into durable, semantically-searchable KG memory — each result becomes a :Document (plus :SearchQuery and :SearchEngine typed nodes with :resultOf / :fromEngine links) so…
nextcloud-ingest
Natively ingest Nextcloud files into the epistemic-graph knowledge graph via the nextcloud-agent MCP server — fetch a file over WebDAV and store its raw bytes as a content-addressed :Blob/:AssetOccurrence plus its extracted text (pdf/office/txt or image OCR) as a linked :Document. Use when the agent must make a…
pipefy-api-fallback
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…
pipefy-ipaas
Use when the user wants to build, test, publish, or manage iPaaS (Advanced Automations) flows: multi-step integrations with external apps (Slack, Gmail, Google Sheets), incoming webhooks, schedules, routers, code steps, or iPaaS data tables. Driven through a per-pipe catalog discovered at runtime. For native if/then…