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 maksimzayats/specx --skill specx-add-core-servicegit clone --depth 1 https://github.com/maksimzayats/specxWrote 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/maksimzayats/specx/specx-add-core-service)<a href="https://agentmods.dev/skills/maksimzayats/specx/specx-add-core-service"><img src="https://agentmods.dev/badge/skills/maksimzayats/specx/specx-add-core-service/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/maksimzayats/specx/specx-add-core-service"><img src="https://agentmods.dev/badge/skills/maksimzayats/specx/specx-add-core-service.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.00562 |
| Opus 5 | $0.00033 | $0.00281 |
| Sonnet 5 | $0.00013 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
specx-add-core-service 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specx Add Core Service
Use this skill for reusable core behavior that is smaller than an application
action. Read references/service.md before writing the service.
Workflow
- Confirm this is reusable business/application behavior, not a small
replaceable ability. Use
BaseCapabilityinstead for one narrow injectable thing. - Name the behavior, not a vague role, and always use the
Servicesuffix:InvoicePricingService,AccessPolicyService,OrderAllocationService,SubscriptionRenewalService. - Put it under
core/<scope>/services/<behavior>.py. - Choose exactly one foundation base:
BasePureService,BaseReadService, orBaseEffectService. - Do not add or use a generic
BaseService. - Inject concrete project collaborators when there is one implementation.
- Inject ports/ABCs only for external IO, framework-bound dependencies, or multiple real implementations. Do not create an interface only to make a concrete collaborator mockable.
- Add a docstring that explains the service scope and includes a concrete
Example:. - Keep methods keyword-only after
self. - Do not open UoW scopes in services. Use cases own transaction lifecycle and pass active UoWs into read/effect services when needed.
- Add flat unit tests that receive the native pytest
containerfixture, register local doubles or inline mocks before resolution, and resolve the service withcontainer.resolve(ServiceClass).
Operational probe services may live under core/health when readiness checks
any required external dependency or policy is reused across deliveries.
Keep simple process liveness in delivery. Use a pure service for reusable
liveness policy and a read service for readiness coordination. Readiness
services depend on gateway ports, not SQLAlchemy, Redis, SDKs, or delivery
frameworks directly. Technical readiness adapters must bound external checks
with short timeouts so a probe cannot hang indefinitely.
Code Style
Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 54 lines · 66 tokens per session scan A eda98f7e88f0
specx-add-core-service is a skill published in the GitHub repository maksimzayats/specx (201 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 562 once invoked, about $0.0003 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-30.
Other skills, from other repositories
spec-kitty-orchestrator-api-operator
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external…
api-design
Design or review an HTTP/REST/GraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to "design an API", "shape the endpoints", "design the schema", "add a new endpoint", "review this API", or when building/modifying a public…
create-mcp-server
Build, iterate, and evaluate Model Context Protocol (MCP) servers that expose external services as tools an LLM can call. Covers schema/tool design, error handling, pagination, MCP Inspector testing, and an eval set. Use when asked to "build an MCP server", "create an MCP tool", "wrap this API as MCP", "expose X to…
spk-integrate-orchestrator-api
Use Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands.
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
backend-conventions
Backend convention reference (.NET 10 / C# 13). Auto-injected into backend-aware agents - not user-invocable.