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 skills add fxckcode/mcp-cor --skill cor-api-toolsgit clone --depth 1 https://github.com/fxckcode/mcp-corWrote 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/fxckcode/mcp-cor/cor-api-tools)<a href="https://agentmods.dev/skills/fxckcode/mcp-cor/cor-api-tools"><img src="https://agentmods.dev/badge/skills/fxckcode/mcp-cor/cor-api-tools/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.
<a href="https://agentmods.dev/skills/fxckcode/mcp-cor/cor-api-tools"><img src="https://agentmods.dev/badge/skills/fxckcode/mcp-cor/cor-api-tools.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.03861 |
| Opus 5.5 | $0.00013 | $0.01544 |
| Sonnet 5.5 | $0.00007 | $0.00772 |
| Haiku 4.5 | $0.00003 | $0.00386 |
Grade A, and why
cor-api-tools 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 1mo 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 — 696 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COR API Tools — Complete Reference
All tool names are prefixed with cor_. Every tool returns a JSON string. All async functions use httpx under the hood with automatic Bearer token injection via get_client().
Projects Module (14 tools)
cor_list_projects
List projects with optional filters.
Arguments:
| Arg | Type | Default | Description |
|---|---|---|---|
page |
int | 1 | Page number |
per_page |
int | 20 | Results per page |
filters |
dict or None | None | Filter fields: clientId, status, health, startDate, endDate |
Example call:
await cor_list_projects(
page=1,
per_page=10,
filters={"status": "active", "clientId": 42}
)
Response shape:
{
"data": [
{
"id": 1,
"name": "Website Redesign",
"clientId": 42,
"status": "active",
"health": "on_track",
"startDate": "2025-01-01",
"endDate": "2025-06-30",
"description": "Complete website overhaul"
}
],
"totalPages": 1,
"page": 1,
"perPage": 10
}
cor_get_project
Get a single project by ID.
Arguments: project_id (int | str) — The project ID.
Example call:
await cor_get_project(project_id=42)
cor_create_project
Create a new project.
Arguments: data (dict) — Fields: name (required), clientId, description, startDate, endDate, status.
Example call:
await cor_create_project(data={
"name": "New Campaign",
"clientId": 42,
"description": "Q3 marketing campaign",
"startDate": "2025-07-01",
"endDate": "2025-09-30",
"status": "active"
})
cor_update_project
Partial update an existing project.
Arguments: project_id (int | str), data (dict) — Fields to update.
cor_delete_project
Delete a project.
Arguments: project_id (int | str).
cor_get_project_collaborators
Get collaborators for a project.
Arguments: project_id (int | str).
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.
- 1mo ago First seen · 696 lines · 33 tokens per session scan A e7a8a74ba25a
cor-api-tools is a skill published in the GitHub repository fxckcode/mcp-cor (0 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 3,861 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
exploring-tables
Exploring any ServiceNow table: schema, field types, sample records, relationships, and data patterns. Use when the user mentions tables, schemas, fields, data dictionary, sysdictionary, sysdbobject, table structure, 'what fields does X have', or wants to understand a ServiceNow table they haven't worked with before.
assessing-change-impact
Assessing what a ServiceNow change request touched and what followed it: affected CIs, other changes on the same CIs in an overlapping window, and incidents on those CIs after the change, without trusting hidden incident-to-change links. Use this skill whenever the user asks whether a change (a CHG number) caused or…