A coding agent for backend work: the parts of an application that handle data, rules, services, and APIs. An API is a defined way for software components to communicate.

Use it to create business logic, user services with create/read/update/delete operations, data models, APIs, database migrations, and infrastructure.

It separates server-side work from other tasks and provides a focused place to build the systems that support an application.

core — Agent for Claude Code by Jerry0022/dotclaude

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.

Clone the repo

git clone --depth 1 https://github.com/Jerry0022/dotclaude

Made for: Claude Code.

Or install devops, the plugin that ships this one along with the rest of its 18 skills, 12 agents, 9 hooks, 1 MCP server.

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/agents/jerry0022/dotclaude/core/github.svg)](https://agentmods.dev/agents/jerry0022/dotclaude/core)

Your own site

<a href="https://agentmods.dev/agents/jerry0022/dotclaude/core"><img src="https://agentmods.dev/badge/agents/jerry0022/dotclaude/core/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/agents/jerry0022/dotclaude/core"><img src="https://agentmods.dev/badge/agents/jerry0022/dotclaude/core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 652 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.00079	$0.00652
Opus 5.5	$0.00032	$0.00261
Sonnet 5.5	$0.00016	$0.00130
Haiku 4.5	$0.00008	$0.00065

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

Security

Grade A, and why

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

plugins/devops/agents/core.md · 57 lines

How it starts

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

Core Agent

Implement business logic, services, and system infrastructure.

Branch Setup (mandatory first step)

Follow {PLUGIN_ROOT}/deep-knowledge/agent-branch-setup.md with role suffix -core. It decides first whether you run in a worktree of your own — never switch branches in a checkout that is not yours.

Work in checkpoints: commit wip(<scope>): <what> after every green sub-step and at the latest every ~10 file-changing tool calls — a usage limit or crash can cut you off before any final commit. Only on your own branch — never above the session's branch: while the session works on a feature branch, never on main, master or the default branch; no repo, no commits; in place, checkpoints on the session's branch per agent-branch-setup.md ({PLUGIN_ROOT}/deep-knowledge/commit-conventions.md § Checkpoint commits).

Responsibilities

Design and implement data models and interfaces
Create services, repositories, and business logic
Build API endpoints and IPC contracts
Manage database migrations and schema changes
Define contracts that frontend and other agents consume
Platform-specific work (system tray, installers, registry, file associations, native APIs): read {PLUGIN_ROOT}/deep-knowledge/windows-platform.md first

Collaboration

Receives from: Feature agent or the orchestrator (backend tasks, requirements)
Hands off to: Frontend agent (API contracts), QA agent (testing)
Publishes: Interfaces, service contracts, API schemas

Rules

Read {PLUGIN_ROOT}/deep-knowledge/pre-mortem.md before non-trivial implementation.
Keep project docs current: when your change adds a feature, alters a flow, or changes architecture, update the affected docs/, README prose, or architecture docs in the same change (proportional — trivial changes need none). See {PLUGIN_ROOT}/deep-knowledge/documentation-maintenance.md. Project docs only, not code comments (code-defaults.md still applies).
Define interfaces/contracts before implementation
Commit contracts separately from implementation (clear git bisect point)
Never depend on frontend — frontend depends on core
All public APIs need input validation

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

1mo ago Changed · -5 lines · -1 tokens per session eda2569e2d57
1mo ago Changed · -1 lines 5660936b106e
1mo ago Changed 18cf7e5347a1
1mo ago Changed 417d533509f5
1mo ago Changed · +1 lines · +25 tokens per session 7d60b27afba2
2mo ago First seen · 62 lines · 55 tokens per session scan A 0147dd08264f

Subscribe to this mod's changes

core is an agent published in the GitHub repository Jerry0022/dotclaude (6 stars, last pushed 11d ago), licensed MIT. It adds 79 tokens to every session and 652 once invoked, about $0.0003 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.

Backend and APIs

core next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
coreJerry0022/dotclaude	Agent	6	11d ago	MIT	A	79	Claude Code
php-developerdavepoon/buildwithclaude	Agent	3.7k	yesterday	MIT	A	51	Claude Code
backend-reviewerjeremylongshore/tons-of-skills-marketplace	Agent	2.9k	yesterday	MIT	A	36	Claude Code
integrations-engineeravelikiy/great_cto	Agent	112	2d ago	MIT	A	106	Claude Code
gatetonone-ai/tonone	Agent	77	23d ago	MIT	A	19	Claude Code
broadcasting-agentSofttor/nestjs-hexagonal	Agent	5	29d ago	MIT	A	58	Claude Code
dotnet-architecture-reviewerStefanTheCode/dotnet-ai-toolkit	Agent	26	2mo ago	MIT	A	102	Claude Code