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 umputun/cc-thingz --skill md-copygit clone --depth 1 https://github.com/umputun/cc-thingzWrote 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/umputun/cc-thingz/md-copy)<a href="https://agentmods.dev/skills/umputun/cc-thingz/md-copy"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/md-copy.svg" alt="Measured on agentmods" 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.00044 | $0.00374 |
| Opus 5 | $0.00022 | $0.00187 |
| Sonnet 5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
md-copy 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 8d 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.
What it actually says
Markdown Copy
Extract the final answer from this session, convert it to proper markdown format, and copy to clipboard.
Formatting Rules
- No heading elements (
#,##, etc.) — use bold for section titles instead - Convert any ASCII tables to proper markdown tables
- Use italic for emphasis and minor notes
- Preserve code blocks with proper language tags
- Keep bullet lists and numbered lists
- Remove any leading spaces or bullet headers (bullet-style)
- Give the content a nice descriptive title (as bold text, not heading)
Workflow
- Identify the final answer/response in this session
- Format it according to the rules above
- Write formatted text to a timestamped temp file:
tmpfile="/tmp/claude-md-copy-$(date +%s).txt"
cat > "$tmpfile" << 'EOF'
<formatted content>
EOF
- Copy to clipboard and remove temp file:
if [[ "$OSTYPE" == "darwin"* ]]; then
pbcopy < "$tmpfile"
elif command -v xclip &> /dev/null; then
xclip -selection clipboard < "$tmpfile"
elif command -v xsel &> /dev/null; then
xsel --clipboard --input < "$tmpfile"
else
echo "No clipboard tool found" >&2
fi
rm -f "$tmpfile"
- Report success with character count
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.
- 8d ago First seen · 46 lines · 44 tokens per session scan A af7597d12bcb
md-copy is a skill published in the GitHub repository umputun/cc-thingz (468 stars, last pushed 14d ago), licensed MIT. It adds 44 tokens to every session and 374 once invoked, about $0.0002 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
plugin
Manage Claude Code plugins — add marketplaces, install, update, remove, list. Use when installing plugins, checking status, or managing the registry.
flow-next-interview
In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.