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/elgorro/aiquila/claude-mdgit clone --depth 1 https://github.com/elgorro/aiquilaWrote 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/elgorro/aiquila/claude-md)<a href="https://agentmods.dev/instructions/elgorro/aiquila/claude-md"><img src="https://agentmods.dev/badge/instructions/elgorro/aiquila/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.02118 | $0.02118 |
| Opus 5 | $0.01059 | $0.01059 |
| Sonnet 5 | $0.00424 | $0.00424 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
aiquila CLAUDE.md 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 5d 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.
curl -s -u testuser:'AIquila2026!dev' -H 'OCS-APIRequest: true' \ How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIquila — Claude Code Configuration
Project Overview
Monorepo with two independently versioned components:
mcp-server/— TypeScript/Node.js MCP server (npm package:aiquila-mcp, admin account:aiquilaon npmjs.com; versioned inpackage.json)nextcloud-app/— PHP 8.4 Nextcloud app (Composer, versioned inappinfo/info.xml)
Docs live in docs/. Docker environments in docker/ (dev: installation/, prod: standalone/).
Key Commands
All MCP server commands run from mcp-server/:
npm run build # compile TypeScript → dist/
npm run dev # hot reload via tsx (stdio transport by default)
npm test # vitest unit tests
npm run lint # eslint (warnings ok, errors fail CI)
npm run format # prettier --write src/ (auto-fix formatting)
npx prettier --check src/ # check only — run before committing
CI requires both npm run lint and npx prettier --check src/ to pass.
Always run npm run format after editing TypeScript files.
HTTP transport locally:
MCP_TRANSPORT=http npm run dev # serves at http://localhost:3339/mcp
Docker (standalone — external Nextcloud):
cd docker/standalone && make up
make logs-follow
make test
Nextcloud app — static analysis
Psalm runs over lib/ at errorLevel=3 and CI fails on any error:
cd nextcloud-app && composer psalm
OCP\* resolves through vendor/nextcloud/ocp (parsed via <extraFiles>); the private
OC\ classes the app touches are stubbed in tests/stubs/. There is no baseline — fix
findings rather than adding one.
Nextcloud app — OpenAPI spec
After editing a controller annotated with #[OpenAPI], regenerate and commit the spec
(CI fails on a mismatch):
cd nextcloud-app && vendor/bin/generate-spec # updates openapi.json + openapi-full.json
Nextcloud app — local dev testing
To test working-tree changes in the dev stack (docker/installation/) and check for
runtime errors:
cd docker/installation
make build-tarball # repackage nextcloud-app/ from the working tree
make up # IMPORTANT: rebuilds the image with the new tarball
# The post-install hook only runs on first install, so re-extract manually after a recreate:
docker compose exec -T nextcloud bash /docker-entrypoint-hooks.d/post-installation/aiquila-install.sh
docker compose exec -T nextcloud su -p www-data -s /bin/sh -c "php /var/www/html/occ upgrade" # if migrations changed
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.
- 5d ago First seen · 186 lines · 2,118 tokens per session scan A f50de0f54605
aiquila CLAUDE.md is an instructions file published in the GitHub repository elgorro/aiquila (34 stars, last pushed yesterday), licensed MIT. It adds 2,118 tokens to every session, about $0.0106 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-30.
Other instructions, from other repositories
android AGENTS.md
AGENTS.md instructions for nextcloud/android, covering agents.md, your role, project overview, project structure: ai agent handling guidelines and agent skills.
android CLAUDE.md
Claude Code instructions for nextcloud/android, a project described as: 📱 Nextcloud Android app.
nextcloud-mcp-server CLAUDE.md
Claude Code instructions for cbcoutinho/nextcloud-mcp-server, covering claude.md, coding conventions, async/await patterns, type hints and code quality.
istota CLAUDE.md
Claude Code instructions for istota-project/istota: See @AGENTS.md for project overview, commands, and conventions.
gestion AGENTS.md
AGENTS.md instructions for baimard/gestion: Gestion is a Nextcloud invoicing application.
istota AGENTS.md
AGENTS.md instructions for istota-project/istota, covering istota - claude code bot, project structure, key concepts, identity and prompt layers.