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 skills/aidas-dev/k8s-agent-skills/nextcloud-apinpx skills add Aidas-dev/k8s-agent-skills --skill nextcloud-apigit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-skillsWrote 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/aidas-dev/k8s-agent-skills/nextcloud-api)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/nextcloud-api"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/nextcloud-api.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.00051 | $0.03113 |
| Opus 5 | $0.00026 | $0.01556 |
| Sonnet 5 | $0.00010 | $0.00623 |
| Haiku 4.5 | $0.00005 | $0.00311 |
Grade A, and why
nextcloud-api 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Use when managing Nextcloud users, groups, and apps via the Provisioning API (OCS). Covers user CRUD, group management, app enable/disable, and curl examples. NOT for Helm deployment — use nextcloud-helm. How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nextcloud Provisioning API
Overview
The Provisioning API enables external systems to create, edit, delete and query user attributes, manage groups, set quotas, query storage, and manage apps. Enabled by default. Uses the OCS API endpoint format.
Base URL: https://nextcloud.example.com/ocs/v1.php/cloud
Auth: Basic HTTP Auth (admin username:password) + OCS-APIRequest header
Headers (required for ALL calls):
Authorization: Basic <base64(admin:password)>OCS-APIRequest: true- POST requests also require
Content-Type: application/x-www-form-urlencoded
Output format: XML by default. Append ?format=json for JSON.
Users
Add a New User
curl -X POST "https://nextcloud.example.com/ocs/v1.php/cloud/users" \
-H "Authorization: Basic $(echo -n 'admin:password' | base64)" \
-H "OCS-APIRequest: true" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "userid=newuser" \
-d "password=SecurePass123!" \
-d "displayName=New User" \
-d "[email protected]" \
-d "groups[]=admin" \
-d "groups[]=group1" \
-d "quota=10GB"
Status codes: 100=ok, 101=invalid, 102=already exists, 104=group missing
List Users
curl -X GET "https://nextcloud.example.com/ocs/v1.php/cloud/users?search=filter&limit=100&offset=0" \
-H "Authorization: Basic $(echo -n 'admin:password' | base64)" \
-H "OCS-APIRequest: true" | python3 -c "import sys, xml.etree.ElementTree as ET; print('\n'.join(e.text for e in ET.parse(sys.stdin).findall('.//users/element')))"
Get Single User
curl -X GET "https://nextcloud.example.com/ocs/v1.php/cloud/users/newuser" \
-H "Authorization: Basic $(echo -n 'admin:password' | base64)" \
-H "OCS-APIRequest: true" | python3 -c "
import sys, xml.etree.ElementTree as ET
root = ET.parse(sys.stdin).find('.//data')
for child in root:
if child.tag == 'groups':
print(f'{child.tag}: {[e.text for e in child]}')
elif child.text and child.text.strip():
print(f'{child.tag}: {child.text.strip()}')
"
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 · 315 lines · 51 tokens per session scan A fa2021f9ca4d
nextcloud-api is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 3,113 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…