What is list-my-plugin?

A guide for adding a coding-agent extension to an awesome-ai-plugins README, a catalogue file that lists community tools. It checks for duplicates, writes one correctly placed line, and explains when the owner must submit the change.

Use it to prepare a plugin, skill, or MCP server entry, verify the source repository, and identify the correct catalogue section.

It prevents duplicate or misplaced listings and avoids making a repository submission on someone else's behalf.

list-my-plugin — Skill for Claude Code and Codex by hashgraph-online

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/hashgraph-online/awesome-ai-plugins

agentmods

npx agentmods add skills/hashgraph-online/awesome-ai-plugins/list-my-plugin

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin/github.svg)](https://agentmods.dev/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin)

Your own site

<a href="https://agentmods.dev/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-ai-plugins/list-my-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 840 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.00840
Opus 5.5	$0.00023	$0.00336
Sonnet 5.5	$0.00011	$0.00168
Haiku 4.5	$0.00006	$0.00084

Measured 2d ago against content hash c38e791e6df1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

list-my-plugin 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 2d 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.

.agents/skills/list-my-plugin/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

List my plugin

Prepare one listing for the person you are working for. They own the decision to submit: open the pull request from their account only when they asked you to, and never claim, sign up or buy anything on their behalf.

1. Check it is not already listed

grep -in "github.com/OWNER/REPO" README.md

A match is a duplicate only when an existing line names this plugin. A repository can hold several plugins, one line each, so compare the display names. If this plugin is listed, stop and tell your user where. Update an existing line only when they asked for a change.

2. Write the line

One line, one sentence, no marketing superlatives:

- [Plugin Name](https://github.com/OWNER/REPO) - What it does for the user, in one sentence.

Link the source repository, not a website or a fork.
The repository must be public and contain the plugin, skill or server.

3. Pick the section

Under ## Community Plugins in README.md:

What it is	Section
A skill (`SKILL.md`)	`### Agent Skills`
A plugin for one client only (Grok, Kimi, DeepSeek Harness, OpenCode, ZCode)	That client's `### ... Plugins` subsection
Coding, review, testing, git, CI and other developer workflow	`### Development & Workflow`
Everything else: MCP servers, connectors, data and service tools	`### Tools & Integrations`

CONTRIBUTING.md has the extra rules for native skills, MCP servers and each client's submissions. Read the matching part before writing the line.

4. Place it alphabetically and check

Insert the line in alphabetical order by name within its section, then run:

python3 scripts/check-alphabetical.py README.md

Optional source preflight, from the plugin's own repository:

pipx run plugin-scanner lint .
pipx run plugin-scanner verify .

Change only README.md. Do not edit plugins.json or .agents/plugins/; they are generated.

5. Hand over

Commit on a new branch with a message like Add Plugin Name. Then open the pull request if your user asked you to, or give them the branch and this title. The pull request runs a required source scan (score of at least 75) and posts its result as a comment and a check.

Read the full file on GitHub · 90 lines

Changes

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.

2d ago First seen · 90 lines · 57 tokens per session scan A c38e791e6df1

Subscribe to this mod's changes

list-my-plugin is a skill published in the GitHub repository hashgraph-online/awesome-ai-plugins (989 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 840 once invoked, about $0.0002 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-11-05.

Building agents Claude Code ai-assistant awesome awesome-list codex extensions

list-my-plugin next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
list-my-pluginhashgraph-online/awesome-ai-plugins	Skill	989	yesterday	Apache-2.0	A	57	Claude Code, Codex
lockheed-martintheneoai/awesome-skills	Skill	197	5mo ago	none	A	14	Claude Code, Codex
northrop-grummantheneoai/awesome-skills	Skill	197	5mo ago	none	A	14	Claude Code, Codex
raytheontheneoai/awesome-skills	Skill	197	5mo ago	none	A	17	Claude Code, Codex
cheftheneoai/awesome-skills	Skill	197	5mo ago	none	A	66	Claude Code, Codex
low-altitude-traffic-engineertheneoai/awesome-skills	Skill	197	5mo ago	none	A	63	Claude Code, Codex
satellite-communication-engineertheneoai/awesome-skills	Skill	197	5mo ago	none	A	73	Claude Code, Codex