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 RashadAnsari/myagents --skill plugin-authoringgit clone --depth 1 https://github.com/RashadAnsari/myagentsWrote 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/rashadansari/myagents/plugin-authoring)<a href="https://agentmods.dev/skills/rashadansari/myagents/plugin-authoring"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/plugin-authoring/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/rashadansari/myagents/plugin-authoring"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/plugin-authoring.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00078 | $0.01178 |
| Opus 5.5 | $0.00031 | $0.00471 |
| Sonnet 5.5 | $0.00016 | $0.00236 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
plugin-authoring 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Authoring
Rules for writing skills and agents. Apply them when creating or editing any of these files.
Universal Rules
- Assume the model is already smart. Only write what it does not already know: project facts, exact procedures, output contracts. Cut explanations of general concepts. Challenge every line: "does this justify its token cost?"
- Write descriptions in third person, stating both what the artifact does and when to use it. Include the trigger phrases a user would naturally say. Put the key use case first: listings truncate long descriptions.
- Use one consistent term per concept throughout a file. Do not mix synonyms.
- No time-sensitive content. Nothing that becomes wrong on a date.
- Forward slashes in all paths.
- Platform-neutral wording: the same file must read correctly in every editor that loads it. No editor-specific product names or jargon in prose.
- Never reference another plugin file by repo-relative path. The install location differs from the source repo. Invoke skills by name and locate scripts via the plugin or skill root variable.
Skills
Frontmatter: name (lowercase letters, numbers, hyphens, max 64 chars) and description (max 1024 chars, non-empty). Everything else is optional.
- Keep the body under 500 lines. When approaching the limit, split detail into supporting files in the skill directory and link them from SKILL.md, one level deep only. Give reference files longer than 100 lines a table of contents.
- Match specificity to fragility. Judgment tasks get short, high-freedom guidance. Fragile sequences get exact commands with "do not modify" instructions. One default approach with an escape hatch beats a menu of options.
- For multi-step workflows, write numbered steps. For quality-critical output, build a feedback loop: produce, validate, fix, repeat until the validator passes.
- Side-effect or high-cost workflows the user must trigger themselves (commit, deploy, publish) set
disable-model-invocation: true. The model then cannot see the skill at all, so the user must type its/command. Codex ignores that flag, so also addagents/openai.yamlbesideSKILL.mdwithpolicy: allow_implicit_invocation: false. Cursor has had a bug where plugin skills with the flag vanish from the/menu; if they do, that is the cause. Background knowledge that is not a meaningful action: setuser-invocable: false. - Bundled scripts: instruct execution, not reading, unless the algorithm itself is the reference. Scripts must handle their own error cases instead of failing back to the model, and every constant needs a justifying comment.
- A loaded skill stays in context for the whole session. Write standing instructions, not one-time steps.
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.
- 5d ago Changed · -3 tokens per session e06023d0b7c8
- 1mo ago First seen · 58 lines · 81 tokens per session scan A 3d8cbb772675
plugin-authoring is a skill published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,178 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.
Other skills, from other repositories
council-creator
Expert-council meeting protocol. Given a Brief + a persona cast (from persona-generator), propose the council to the Team Manager, and once convened FACILITATE it: each round post a NEW group message that @-mentions the persona-agents by their ASCII usernameSlug, collect their independent replies, stage-summarize…
persona-generator
Given a Council Brief, produce persona-ROLE instance definitions: real, publicly-verifiable people who occupy distinct stakeholder positions on the issue — each a persona-flavored role template (lens / voice / SOUL + the persona-skill capability boundary + icon + an ASCII usernameSlug), handed to convene…
release-db-config-sync
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
design-review
Five-dimension design audit (frontend UI/UX · server data-model & flow · endpoint spec · daemon-runtime/SDK & local-cache-first · built-in skill/agent-role), executed by a NON-implementing agent. Every dimension gets a verdict; N/A only with a stated reason. A dimension the design silently skipped must be surfaced as…
codebase-design
Design maintainable module interfaces, review scoped code changes, and simplify implementations with behavioral verification. Use for code review, cleanup, testability, and module design work.