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/eric861129/SKILLS_All-in-oneWrote 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/eric861129/skills_all-in-one/pypict-claude-skill)<a href="https://agentmods.dev/plugins/eric861129/skills_all-in-one/pypict-claude-skill"><img src="https://agentmods.dev/badge/plugins/eric861129/skills_all-in-one/pypict-claude-skill/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/eric861129/skills_all-in-one/pypict-claude-skill"><img src="https://agentmods.dev/badge/plugins/eric861129/skills_all-in-one/pypict-claude-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pict-test-designer 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
{
"name": "pict-test-designer",
"description": "Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected results.",
"version": "1.0.0",
"author": {
"name": "Omar Kamal Hosney",
"email": "[email protected]"
},
"homepage": "https://github.com/omkamal/pypict-claude-skill",
"repository": {
"type": "git",
"url": "https://github.com/omkamal/pypict-claude-skill.git"
},
"license": "MIT",
"keywords": [
"testing",
"pict",
"pairwise",
"combinatorial",
"test-design",
"test-cases",
"quality-assurance"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 70 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 8d ago First seen · 25 lines scan A 29b4370a474a
pict-test-designer is a plugin published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo 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-09-03.
Other plugins, from other repositories
workflow-skills
Issue triage, TDD, CI fix-with-memory, design-system guard, PR review, dead-code and doc-rot cleanup, comment and test reaping, code-health and visual-QA audits, evidence-checked claims, worktree setup, project bootstrap, cross-provider skill parity, and session wrap-up skills.
ai-stack
Useful AI things an engineer uses daily. Ships prodcheck (senior-engineer production review), prodtest (senior-QA test pass with Playwright), mergemain (context-aware merge of main into the current branch), and shipit (clean commits and PRs, with or without AI attribution).
swift-testing-pro
Swift Testing framework: @Test, #expect, traits, parameterized tests, XCTest migration.
api-forge
Generate API test suites, create mock servers, run contract tests, and benchmark endpoints.
cli-testing
Generate CLI integration testing.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.