PinMe is a zero-configuration command-line tool for creating and deploying full-stack web projects with a frontend, Worker backend, and database, as well as uploading static sites. Developers and coding agents use it to launch or update frontend applications and their supporting services from one command. Its catalogue skills and instructions describe agent workflows for deploying with PinMe.
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 glitternetwork/pinme --skill pinme-sharegit clone --depth 1 https://github.com/glitternetwork/pinmeWrote 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/glitternetwork/pinme/pinme-share)<a href="https://agentmods.dev/skills/glitternetwork/pinme/pinme-share"><img src="https://agentmods.dev/badge/skills/glitternetwork/pinme/pinme-share/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/glitternetwork/pinme/pinme-share"><img src="https://agentmods.dev/badge/skills/glitternetwork/pinme/pinme-share.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00075 | $0.01023 |
| Opus 5 | $0.00037 | $0.00511 |
| Sonnet 5 | $0.00015 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
pinme-share 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 9d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PinMe Share
Create a polished static share artifact, upload it with pinme upload, and return the final URL.
When to Use
Use this skill when the user asks to:
- Share or publish a result using PinMe.
- Create a static page that wraps a deployed project link, demo, report, or artifact.
- Summarize a Codex conversation/session and share it as a page.
- Turn a project handoff into a public landing or summary page.
- Upload an existing static file or folder for lightweight distribution.
If the user needs a backend, database, auth, email, or LLM functionality, use the main pinme skill and any relevant PinMe integration skill first. Use pinme-share at the end to package and publish the result.
Core Workflow
- Identify what is being shared:
- PinMe/full-stack project: deployed URL, short description, key features, tech stack, usage notes.
- Codex conversation: goal, decisions, implementation summary, important outputs, next steps.
- Static file/report/demo: title, purpose, file contents or preview, context for the recipient.
- Create a static share artifact:
- Prefer a single self-contained
index.html. - Use
share/<slug>/index.htmlin the current workspace unless the repo has an existing output/share convention. - Keep CSS inline for portability.
- Do not require JavaScript unless interaction is valuable.
- Prefer a single self-contained
- Sanitize before publishing:
- Remove secrets, tokens, API keys,
.envvalues, internal-only URLs, private user data, and unrelated logs. - For conversation summaries, summarize rather than dumping raw transcript unless the user explicitly asks for verbatim sharing.
- Make links explicit and clickable.
- Remove secrets, tokens, API keys,
- Upload with PinMe:
pinme upload share/<slug> - Return the URL printed by PinMe. If PinMe outputs multiple URLs, prefer DNS domain, then PinMe subdomain, then short URL, then full preview URL. Never truncate hash fragments.
Share Page Content
For a project share page, include:
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.
- 9d ago First seen · 119 lines · 75 tokens per session scan A 49c06afeb132
pinme-share is a skill published in the GitHub repository glitternetwork/pinme (3,739 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,023 once invoked, about $0.0004 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
gh-pages-deploy
Deploy static or interactive frontend content to GitHub Pages using gh CLI. Use when the user wants to publish, share, or make accessible any HTML/CSS/JS content - including demos, prototypes, visualizations, landing pages, portfolios, documentation, interactive tools, games, or any browser-based project. Activate…
redteam-cors-miscfg-detail-pack
Domain routing and boundary guidance for authorized CORS misconfiguration testing, including reflected origins, null origins, subdomain trust, and credential exposure. Use when a task belongs to the CORS testing domain and needs scope, evidence, pivot, or exit criteria.
sprite-gen
Generate clean 2D game sprites and animation atlases with a component-row pipeline: base identity, numeric sprite-request SSoT, per-state layout guides, image-gen row strips, chroma-key alpha cleanup, connected-component frame extraction, cell-based atlas composition, QA reports, and runtime manifest framelayout. Its…
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.
spacing-system
Create a spacing scale from a base unit with rules for when each step applies. Use when standardising padding and margins. For page-level columns and gutters, use layout-grid.