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 cwinvestments/memstack --skill marketplace-submitgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/marketplace-submit)<a href="https://agentmods.dev/skills/cwinvestments/memstack/marketplace-submit"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/marketplace-submit/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/cwinvestments/memstack/marketplace-submit"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/marketplace-submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.01213 |
| Opus 5.5 | $0.00027 | $0.00485 |
| Sonnet 5.5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
memstack-marketing-marketplace-submit 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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace Submit: Preparing marketplace submission...
Step-by-step guide to submit skills, plugins, or tools to community marketplaces via pull request.
Activation
| Trigger | Status |
|---|---|
| User says "submit to marketplace" or "publish my skill" | ACTIVE |
| User says "share this skill" or "list on marketplace" | ACTIVE |
| User says "submit plugin" or "publish to community" | ACTIVE |
| User wants to build a skill | NOT this skill: use Forge |
| User wants to write plugin code | NOT this skill: use standard development |
Context Guard
- Do NOT use for skill creation (that's Forge)
- Do NOT use for plugin development
- Do NOT use for npm publishing (different workflow)
- This skill ONLY handles marketplace submission via PR
Target Marketplaces
| Marketplace | URL | Format | Submission |
|---|---|---|---|
| buildwithclaude | github.com/davepoon/buildwithclaude | Skills/plugins directory | Fork + PR |
| awesome-mcp-servers | github.com/punkpeye/awesome-mcp-servers | Awesome list | Fork + PR |
| Smithery | smithery.ai | MCP registry | Web submission |
| Glama MCP | glama.ai/mcp/servers | MCP directory | Fork + PR |
| awesome-claude-code | Community repos | Various | Fork + PR |
Steps
Step 1: Prepare the submission package
Verify the skill/plugin is ready:
| Check | How to verify |
|---|---|
| SKILL.md exists and is complete | Read the file, confirm frontmatter + body |
| Name and description are clear | Description explains what it does in one sentence |
| Trigger words are specific | No vague triggers that overlap with other skills |
| No proprietary/Pro content | Confirm this is a free skill or has permission |
| Works locally | User has tested it in their own CC session |
# Verify the skill file exists and has frontmatter
head -10 skills/<category>/<name>/SKILL.md
Step 2: Fork the target repository
# Fork via GitHub CLI
gh repo fork <owner>/<repo> --clone
# Or fork via web UI at github.com/<owner>/<repo>/fork
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.
- 1mo ago Changed 9fd24705e77d
- 1mo ago First seen · 185 lines · 68 tokens per session scan A 2194eda654c2
memstack-marketing-marketplace-submit is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 1,213 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-09-03.
Other skills, from other repositories
ccpm
CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync…
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.