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/vando-sketch/nextcloudmcp/claude-mdgit clone --depth 1 https://github.com/Vando-sketch/NextCloudMCPWrote 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/instructions/vando-sketch/nextcloudmcp/claude-md)<a href="https://agentmods.dev/instructions/vando-sketch/nextcloudmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vando-sketch/nextcloudmcp/claude-md.svg" alt="Measured on agentmods" 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 | $0.00645 | $0.00645 |
| Opus 5 | $0.00322 | $0.00322 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
NextCloudMCP CLAUDE.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 4d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Git workflow
Follow this for every implementation task, without waiting to be asked:
- Classify the task as
feat(new capability),fix(bug fix), or another conventional type (refactor,chore,docs,test) based on what the diff actually does. - Create a branch named
<type>/<short-kebab-description>(e.g.feat/wardrobe-photo-batching,fix/dashboard-auth-bypass) off the current base branch before making changes. Always create a branch — never commit directly tomainor to whatever branch you started on. - Implement, test, and commit on that branch.
- Open a pull request (
gh pr create) once the work is done and verified (tests + lint pass), targeting the branch you branched from.
Breaking down larger tasks with subagents
For a task large enough to naturally split into independent subtasks:
- Create your own
<type>/<description>branch first, as above — this is the integration branch. - Split the work into subtasks and dispatch each to a subagent, picking the model per subtask's complexity (e.g. a small, mechanical change → a cheaper/faster model; a subtask requiring deep design or judgment → a stronger model).
- Each subagent creates its own branch off the integration branch (same
<type>/<description>naming convention), and independently follows the full workflow above on that branch: implement, test, commit. Subagents do not open their own pull requests and do not merge — only the main agent does. - Once a subagent's branch is done, the main agent merges it into its own integration branch, resolving any conflicts.
- After all subagent branches are merged, the main agent runs the full test suite and lint on the integration branch, then opens the single pull request for the whole task.
Timezone & Date Conventions
BREAKING CHANGE: Timezone handling changed from hardcoded UTC to configurable server default timezone (
MCP_DEFAULT_TIMEZONE, defaultEurope/Berlin).
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.
- 4d ago First seen · 50 lines · 645 tokens per session scan A 3e66b742b601
NextCloudMCP CLAUDE.md is an instructions file published in the GitHub repository Vando-sketch/NextCloudMCP (0 stars, last pushed 10d ago), licensed MIT. It adds 645 tokens to every session, about $0.0032 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-09-01.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).