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 skills/sifxprime/kodelyth-ecc/api-connector-buildernpx skills add sifxprime/kodelyth-ecc --skill api-connector-buildergit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/api-connector-builder)<a href="https://agentmods.dev/skills/sifxprime/kodelyth-ecc/api-connector-builder"><img src="https://agentmods.dev/badge/skills/sifxprime/kodelyth-ecc/api-connector-builder.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.00036 | $0.00601 |
| Opus 5 | $0.00018 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
api-connector-builder 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 yesterday.
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.
This is a copy
92% identical to api-connector-builder — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Connector Builder
Use this when the job is to add a repo-native integration surface, not just a generic HTTP client.
The point is to match the host repository's pattern:
- connector layout
- config schema
- auth model
- error handling
- test style
- registration/discovery wiring
When to Use
- "Build a Jira connector for this project"
- "Add a Slack provider following the existing pattern"
- "Create a new integration for this API"
- "Build a plugin that matches the repo's connector style"
Guardrails
- do not invent a new integration architecture when the repo already has one
- do not start from vendor docs alone; start from existing in-repo connectors first
- do not stop at transport code if the repo expects registry wiring, tests, and docs
- do not cargo-cult old connectors if the repo has a newer current pattern
Workflow
1. Learn the house style
Inspect at least 2 existing connectors/providers and map:
- file layout
- abstraction boundaries
- config model
- retry / pagination conventions
- registry hooks
- test fixtures and naming
2. Narrow the target integration
Define only the surface the repo actually needs:
- auth flow
- key entities
- core read/write operations
- pagination and rate limits
- webhook or polling model
3. Build in repo-native layers
Typical slices:
- config/schema
- client/transport
- mapping layer
- connector/provider entrypoint
- registration
- tests
4. Validate against the source pattern
The new connector should look obvious in the codebase, not imported from a different ecosystem.
Reference Shapes
Provider-style
providers/
existing_provider/
__init__.py
provider.py
config.py
Connector-style
integrations/
existing/
client.py
models.py
connector.py
TypeScript plugin-style
src/integrations/
existing/
index.ts
client.ts
types.ts
test.ts
Quality Checklist
- matches an existing in-repo integration pattern
- config validation exists
- auth and error handling are explicit
- pagination/retry behavior follows repo norms
- registry/discovery wiring is complete
- tests mirror the host repo's style
- docs/examples are updated if expected by the repo
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.
- yesterday First seen · 122 lines · 36 tokens per session scan A 969ff3c71153
api-connector-builder is a skill published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 601 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to api-connector-builder, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
foolproof-product
Use this skill on ANY code change in codevira's product surface (mcpserver/, indexer/). Triggers on Edit/Write to product code, on phrases like "fix bug", "add feature", "handle error", or any modification to commands the end-user runs. Enforces 10 product- reliability principles: no silent failures, atomic state…
epistemic-honesty
Use this skill whenever you're about to (1) make a definitive claim like "this works", "tests pass", "ready to ship", "fixed", "done"; or (2) propose a solution to a problem; or (3) diagnose a bug or issue. Forces explicit confidence calibration with inline evidence, surfaces what you don't know, and demands a…
open-source-quality
Use this skill before committing, pushing, or opening a PR. Triggers on phrases like "commit", "git commit", "push", "open PR", "create pull request", "finalize this change". Enforces conventional commit messages, atomic commits, code style (ruff/mypy), public-API docstrings, actionable error messages, changelog…
release-readiness
Use this skill whenever the conversation mentions releasing, shipping, publishing, promoting to PyPI, "ship it", "release X.Y.Z", "ready to release", "let's publish", or any phrase suggesting moving codevira to production. Walks the 5-gate release gauntlet (G1-G5) and refuses to proceed without evidence at every gate.…
development-discipline
Use this skill before ANY code-writing tool call (Edit, Write, NotebookEdit) on this project. Triggers on phrases like "implement", "fix bug", "add feature", "refactor", "create function", "modify file", or whenever the user asks for a code change. Forces a 4-step CONTEXT → PURPOSE → REASON → CODE sequence with…
practical-coding
Use for implementing, fixing, refactoring, or reviewing code with the smallest correct change; routes only unresolved debugging, architecture/choice, or risk-boundary blockers, while code retrieval uses the cheapest sufficient available capability.