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.
git clone --depth 1 https://github.com/nguyenthanhtat/screen1-claudeWrote 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/plugins/nguyenthanhtat/screen1-claude/marketplace)<a href="https://agentmods.dev/plugins/nguyenthanhtat/screen1-claude/marketplace"><img src="https://agentmods.dev/badge/plugins/nguyenthanhtat/screen1-claude/marketplace/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/plugins/nguyenthanhtat/screen1-claude/marketplace"><img src="https://agentmods.dev/badge/plugins/nguyenthanhtat/screen1-claude/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
screen1-claude-skills marketplace 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 4d 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
{
"name": "screen1-claude-skills",
"owner": {
"name": "Nguyen Thanh Tat",
"email": "[email protected]"
},
"metadata": {
"description": "Professional Claude Code skills for Testing, Git workflows, and Web Crawling",
"version": "1.3.0"
},
"plugins": [
{
"name": "screen1-skills",
"source": {
"source": "github",
"repo": "nguyenthanhtat/screen1-claude"
},
"description": "Testing automation, Git workflows, and Web Crawler → Next.js generator",
"version": "3.1.1",
"strict": true
}
]
}The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed 32a047a4acdd
- 6d ago Changed 868eb3ae2510
- 1mo ago First seen · 23 lines scan A f47b5be9d31f
screen1-claude-skills marketplace is a plugin published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
deadeye
Fits model, effort, and context to each task via a deterministic policy kernel behind Claude Code hooks. He doesn't waste shots.
ar
ar — autoresearch: a skill-only autonomous experiment loop. Propose → measure → keep winners → repeat, against any numeric objective, with noise-floor gating so nothing is banked on noise. Five skills: /ar:start opens a run (dedicated branch + baseline noise floor), /ar:resume advances it, /ar:status prints read-only…
sms
Curated bundle of Claude Code skills and commands by Sean Martin Smith.