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 jentic/jentic-one --skill contribute-spec-fixgit clone --depth 1 https://github.com/jentic/jentic-oneWrote 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/jentic/jentic-one/contribute-spec-fix)<a href="https://agentmods.dev/skills/jentic/jentic-one/contribute-spec-fix"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/contribute-spec-fix/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/jentic/jentic-one/contribute-spec-fix"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/contribute-spec-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 58 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 214 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 215 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 143 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00138 | $0.06785 |
| Opus 5.5 | $0.00055 | $0.02714 |
| Sonnet 5.5 | $0.00028 | $0.01357 |
| Haiku 4.5 | $0.00014 | $0.00679 |
Grade A, and why
contribute-spec-fix 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 18d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribute a Spec Fix (Overlay → PR → optional local apply)
Fix a spec in jentic-public-apis the right way: capture the fix as an OpenAPI Overlay,
validate it, and open a PR so the whole community gets the fix. This is the improvement
flywheel — fixes made by AI agents are contributed back, not siloed on one machine.
Target: $ARGUMENTS (a vendor/api id like posthog.com/posthog-api, or a path to a spec).
If the vendor is not in the catalog at all, this is the wrong skill — use import-new-api
instead; this skill only fixes specs that already exist.
The flywheel — read this first
broken spec found
│
▼
write overlay ──► validate (lint + idempotency) ──► apply to openapi.json
│
▼
┌─────────────────────────────────────────────┐
│ DEFAULT: PR to jentic/jentic-public-apis │ ← community gets the fix
└─────────────────────────────────────────────┘
│
▼ (only if the user is blocked on maintainer approval time)
┌─────────────────────────────────────────────┐
│ FALLBACK: apply the SAME overlay to the │ ← unblocks the user now;
│ local Jentic registry — PR stays open │ PR is still the source of truth
└─────────────────────────────────────────────┘
│
▼ (later: the registry keeps watching upstream)
┌─────────────────────────────────────────────┐
│ upstream spec changes ──► registry emits: │
│ • update_available → re-import to adopt│ ← fix merged upstream? adopt + retire
│ • update_conflicts_overlay → operator picks │ ← never silently overwrites the fix
└─────────────────────────────────────────────┘
Always open the PR. The local apply is an impatience valve, not a substitute — it uses the same overlay document, so nothing forks. Never skip the PR just because a local apply worked.
Prerequisites
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.
- 18d ago Changed 28bf8a6fe825
- 19d ago Changed d9bb822fae38
- 27d ago Changed 7be3f6d8ad73
- 1mo ago Changed 682999b54839
- 1mo ago First seen · 504 lines · 138 tokens per session scan A 93e4b47104ff
contribute-spec-fix is a skill published in the GitHub repository jentic/jentic-one (190 stars, last pushed 2d ago), licensed Apache-2.0. It adds 138 tokens to every session and 6,785 once invoked, about $0.0006 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-30.
Other skills, from other repositories
lobu-operator
Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.
maidan-claimant
Take coding work from a Maidan queue as a session claimant. Claims the next task routed to sessions, does it in this checkout, runs the repository's pre-push gate, and hands the change back so Maidan opens the draft pull request, then reports usage, starts review and releases the claim. Use when asked to take, claim…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
github
Manage GitHub issues and pull requests, inspect CI runs, and query repository data.
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…