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/jpantsjoha/ai-native-developer-experience/plugin-submissionnpx skills add jpantsjoha/ai-native-developer-experience --skill plugin-submissiongit clone --depth 1 https://github.com/jpantsjoha/ai-native-developer-experienceWrote 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/jpantsjoha/ai-native-developer-experience/plugin-submission)<a href="https://agentmods.dev/skills/jpantsjoha/ai-native-developer-experience/plugin-submission"><img src="https://agentmods.dev/badge/skills/jpantsjoha/ai-native-developer-experience/plugin-submission.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.00064 | $0.00849 |
| Opus 5 | $0.00032 | $0.00425 |
| Sonnet 5 | $0.00013 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
plugin-submission 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Submission
Treat every public listing as an external representation of the project. Submit only an artifact that the destination's current policy accepts, and retain a receipt for every send.
Workflow
- Classify the destination and artifact. Determine whether it accepts a full
plugin, a repository, or one standalone
SKILL.md. Do not describe a multi-skill plugin as one skill, or split a skill bundle without an explicit portable artifact. - Read the current primary policy. Use the destination's official submission
instructions or
CONTRIBUTING.md; record its URL, access requirements, licence and validation rules, and any limits on automated or AI-assisted submissions. - Validate eligibility. Check the public candidate URL, release/tag, licence as
detected by the hosting platform, manifest/schema validity, documentation, and the
destination-specific validator. Treat a mismatch or unmet requirement as
blocked, not as an invitation to bypass it. - Prepare one destination matrix. For each target, record: destination, artifact,
policy evidence, status (
ready,blocked,deferred, orhuman-only), exact payload, and rollback action. Reuse the canonical repository description; minimise personal data and never add an email without explicit permission. - Stage, then confirm. Fill or draft public data only after the operator has approved the destination. Immediately before clicking a submit control, opening a PR, or sending a recommendation, restate the exact target and payload and obtain a final human confirmation. A single confirmation may cover multiple named sends only when the full set and payloads are shown together.
- Send through the permitted route. Use a form, PR, issue, or API only when the policy permits that route. Never act where a policy requires a human-authored recommendation, prohibits AI-assisted submissions, or requires credentials/access the operator has not supplied.
- Verify and record the receipt. Capture the submission URL/identifier and status. If a listing is rejected or stale, record the reason and next eligible action. Roll back a repository contribution by closing its PR/issue when appropriate; external directory records require the destination's own removal/update path.
What ships with it
1 file 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.
- 4d ago First seen · 69 lines · 64 tokens per session scan A a84626749874
plugin-submission is a skill published in the GitHub repository jpantsjoha/ai-native-developer-experience (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 64 tokens to every session and 849 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
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
comet-hotfix
Comet 预设 —— 通过 open-build-verify-archive 短流程修复已有行为 bug。.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-design
Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
comet-tweak
Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization.