What is NextCloudMCP CLAUDE.md?

A set of Claude Code instructions for the NextCloudMCP repository. It defines Git workflow, task classification, branch naming, testing, commits, pull requests, and when to split larger work among subagents.

Managing implementation tasks in NextCloudMCP, including creating feature or fix branches, running checks, committing changes, and opening pull requests.

It gives the coding agent repository-specific rules so changes follow the project's expected review and collaboration process.

How Vando-sketch/NextCloudMCP configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Vando-sketch/NextCloudMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Vando-sketch/NextCloudMCP/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Vando-sketch/NextCloudMCP

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/vando-sketch/nextcloudmcp/claude-md/github.svg)](https://agentmods.dev/instructions/vando-sketch/nextcloudmcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/vando-sketch/nextcloudmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vando-sketch/nextcloudmcp/claude-md/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 645 This file is loaded in full into every session.

When invoked 645 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00645	$0.00645
Opus 5.5	$0.00258	$0.00258
Sonnet 5.5	$0.00129	$0.00129
Haiku 4.5	$0.00064	$0.00064

Measured 2mo ago against content hash 3e66b742b601, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

CLAUDE.md · 50 lines

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 to main or 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, default Europe/Berlin).

Read the full file on GitHub · 50 lines

Changes

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.

2mo ago First seen · 50 lines · 645 tokens per session scan A 3e66b742b601

Subscribe to this mod's changes

NextCloudMCP CLAUDE.md is an instructions file published in the GitHub repository Vando-sketch/NextCloudMCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 645 tokens to every session, about $0.0026 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-09-01.

NextCloudMCP CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
NextCloudMCP CLAUDE.mdVando-sketch/NextCloudMCP	Instructions file	0	2mo ago	MIT	A	645	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	3d ago	MIT	A	4,313	Codex, OpenCode

NextCloudMCP: Instructions file for Claude Code