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 instructions/tadmstr/nextcloud-mcp/agents-mdgit clone --depth 1 https://github.com/TadMSTR/nextcloud-mcpWhat 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.00559 | $0.00559 |
| Opus 5 | $0.00280 | $0.00280 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
nextcloud-mcp AGENTS.md 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — nextcloud-mcp
What this server does
Exposes Nextcloud operations as MCP tools:
- occ admin — version check, maintenance mode, app management, config, file scan, database maintenance, background jobs, FTS indexing, security check, log tail
- OCS provisioning — user and group management, app password generation
- WebDAV file ops — list, get, put, move, delete
- Share management — create/list/delete public links and user/group shares
Tool groups
| Group | Scope | Tools |
|---|---|---|
| occ-admin | sysadmin | occ_status, maintenance_mode, app_manage, config_get, config_set, files_scan, files_cleanup, db_add_missing_indices, db_convert_bigint, background_jobs, upgrade_check, security_check, fulltextsearch_index, external_storage_list, notify_push_selftest, log_tail, system_check |
| ocs-provisioning | sysadmin | user_list, user_create, user_disable, group_create, group_add_member, app_password_create |
| files | per-agent | dav_list, dav_get, dav_put, dav_move, dav_delete, share_create, share_list, share_delete |
scoped-mcp integration (forge)
In ~/.claude/manifests/:
nextcloud-mcp:
port: 8500
grants:
sysadmin:
- occ-admin
- ocs-provisioning
- files
developer:
- files
research:
- files
writer:
- files
security:
- files
Important notes
config_setcan break Nextcloud. Useconfig_getto read before writing.app_password_createreturns the password once. Store it in Vault immediately.fulltextsearch_index --resetwipes and rebuilds the full OpenSearch index. Takes time.dav_get/dav_putuse base64 encoding for binary content.- WebDAV paths are relative to the user's file root (no leading slash needed).
share_create,share_list,share_deleteauthenticate as admin regardless of calling agent. This is intentional — admin auth is required for cross-user share management via OCS.
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 · 56 lines · 559 tokens per session scan A d3450f277516
nextcloud-mcp AGENTS.md is an instructions file published in the GitHub repository TadMSTR/nextcloud-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 559 tokens to every session, about $0.0028 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.