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 dashaworks/share-as-link-skill --skill share-as-linkgit clone --depth 1 https://github.com/dashaworks/share-as-link-skillWrote 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/dashaworks/share-as-link-skill/share-as-link)<a href="https://agentmods.dev/skills/dashaworks/share-as-link-skill/share-as-link"><img src="https://agentmods.dev/badge/skills/dashaworks/share-as-link-skill/share-as-link/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/dashaworks/share-as-link-skill/share-as-link"><img src="https://agentmods.dev/badge/skills/dashaworks/share-as-link-skill/share-as-link.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.00104 | $0.00865 |
| Opus 5 | $0.00052 | $0.00432 |
| Sonnet 5 | $0.00021 | $0.00173 |
| Haiku 4.5 | $0.00010 | $0.00086 |
Grade A, and why
share-as-link 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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Share as Link
The zero-friction "get me a link" skill. Something worth keeping was just produced — publish it as-is to a live URL and hand the link back. No restructuring, no redesign, no "let me turn this into a report first." That restraint is the whole point: it keeps this a ten-second operation.
When to use
- "Share this / give me a link / put this online / make it a page"
- The user wants the content out of the chat now, not improved
- The output is already in a shape the user is happy with — they just need a URL
When not to use — hand off instead:
- The content should be reshaped into a real document with sections, hierarchy, and charts → report-publisher
- It's going to a specific person and knowing "did they open it?" matters → proposal-tracker
- It's slides → deck-publisher
Offer the handoff when you see the need; don't silently upgrade a "just give me a link" request into a full report.
Steps
- Take the content as-is. Use what was just produced verbatim — the conversation excerpt, the analysis, the markdown, the artifact. Do not rewrite, reorder, or "improve" it. Light cleanup only: a title, and stripping obvious chat scaffolding ("sure, here's…").
- Author minimally. Call
get_design_systemand wrap the content in the design system's basic document shell so it reads well — themed type, spacing, dark mode — but add no structure the source didn't have. For plain markdown,publishMode B (content+type: "report") is the fastest path; for richer content author light HTML. - Lint. Call
lint_documentand fix what it flags. Even the fast path passes lint. - Publish. Call
publish. Return the live URL prominently and plainly — the link is the deliverable. - Then, and only then, offer the upgrades. One short line, not a pitch:
- "Want this designed properly as a report?" → report-publisher
- "Sending it to someone specific and want to know if they open it?" → proposal-tracker
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.
- 10d ago First seen · 62 lines · 104 tokens per session scan A 80e08267aa2c
share-as-link is a skill published in the GitHub repository dashaworks/share-as-link-skill (230 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 865 once invoked, about $0.0005 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
cms-metadata-tagger
Takes a finished piece of content and produces a complete, archive-ready metadata record — including descriptive tags, subject classifications, rights notes, and an archival summary — for entry into a content management or digital archive system.
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
cms-metadata-writer
Writes structured metadata fields — title tag, meta description, tags, category, slug, and Open Graph text — for a CMS entry, optimized for search discoverability and social sharing.
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
igce-builder-cr
Trigger for: cost-reimbursement IGCE, CR cost estimate, CPFF, CPAF, CPIF, cost-plus estimate, BAA estimate, fixed-fee analysis, award-fee analysis, incentive-fee analysis, proposed CR rate validation, cost-pool buildup, share-ratio scenario, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable…