What is reportia-mcp-usage?

Instructions for using the mcp-reportia server, which gives AI agents access to company reporting operations. They cover company identification, pagination, file exports, safety checks, and operations that can change or delete data.

Use them when an agent needs to query or export company reports, resolve a company, work through paginated results, or handle actions that require explicit confirmation.

They reduce mistakes such as using the wrong company ID, skipping pages, mishandling downloaded files, or performing destructive actions without confirmation. They also describe known limits of the server.

reportia-mcp-usage — Skill for Claude Code and Codex by javalenciacai

Install

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.

Any agent

npx skills add javalenciacai/mcp-reportia --skill reportia-mcp-usage

Clone the repo

git clone --depth 1 https://github.com/javalenciacai/mcp-reportia

Made for: Claude Code, Codex.

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/skills/javalenciacai/mcp-reportia/reportia-mcp-usage/github.svg)](https://agentmods.dev/skills/javalenciacai/mcp-reportia/reportia-mcp-usage)

Your own site

<a href="https://agentmods.dev/skills/javalenciacai/mcp-reportia/reportia-mcp-usage"><img src="https://agentmods.dev/badge/skills/javalenciacai/mcp-reportia/reportia-mcp-usage/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/skills/javalenciacai/mcp-reportia/reportia-mcp-usage"><img src="https://agentmods.dev/badge/skills/javalenciacai/mcp-reportia/reportia-mcp-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,853 The whole file, excluding the scripts and references it only reads on demand.

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.00089	$0.01853
Opus 5	$0.00044	$0.00927
Sonnet 5	$0.00018	$0.00371
Haiku 4.5	$0.00009	$0.00185

Measured today against content hash b59b317768f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

reportia-mcp-usage 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 today.

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.

skills/reportia-mcp-usage/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use This Skill

Use this skill whenever you (the AI agent) detect that the mcp-reportia MCP server is available in your tool list (any tool whose name starts with reportia_). This skill is a guardrail, not a replacement for the tools' own descriptions — read each tool's inputSchema before calling it.

Core Conventions

1. CompanyId resolution

Most tools accept companyId as optional.
If you pass companyId, it must be a positive integer.
If you omit it, the MCP uses the env var REPORTIA_COMPANY_ID if set.
If neither is set, the tool fails with MISSING_COMPANY_ID and does NOT call the API. Prefer using reportia_companies_list first to discover valid IDs before guessing.

2. Destructive operations

Tools marked with destructive: true in the MCP server (you can see this in the tool's metadata) require an explicit confirm: true flag in the input. Never send confirm: true without showing the user the exact parameters that will be sent (companyId, resource ID, what will be deleted).

The destructive tools are:

reportia_company_activate
reportia_movements_delete_all (requires confirmationText matching the companyId, plus acknowledgeRisk: true plus confirm: true)
reportia_account_mapping_delete
reportia_salesperson_mapping_delete
reportia_line_group_mapping_delete
reportia_cost_center_mapping_delete
reportia_cost_center_report_delete
reportia_invoice_email_send and reportia_invoices_send_multiple
reportia_company_settings_update
reportia_invoice_settings_create and reportia_invoice_settings_update
reportia_cost_center_report_duplicate
reportia_cost_center_report_execute
reportia_siigo_history_get (server may trigger sync on-demand)

If the LLM (you) sends a destructive tool without confirm: true, the MCP returns a structured error with code: "GUARD_REJECTED" and does NOT call the API.

3. Read-only tools

All reportia_*_list, _get, _search, _settings_get, _history, _trace, _sync_runs_list, _schedules_list, _clients_list etc. do not require confirmation. Use them freely.

Read the full file on GitHub · 164 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.

today Changed · +15 lines b59b317768f7
11d ago First seen · 149 lines · 89 tokens per session scan A e2cf2703f87e

Subscribe to this mod's changes

reportia-mcp-usage is a skill published in the GitHub repository javalenciacai/mcp-reportia (0 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,853 once invoked, about $0.0004 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.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens