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.
/plugin marketplace add izkreny/agentificonpx agentmods add plugins/izkreny/agentifico/gh-sologit clone --depth 1 https://github.com/izkreny/agentificoWrote 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/izkreny/agentifico/gh-solo)<a href="https://agentmods.dev/plugins/izkreny/agentifico/gh-solo"><img src="https://agentmods.dev/badge/plugins/izkreny/agentifico/gh-solo.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gh-solo 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 3d 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": "gh-solo",
"version": "3.0.0",
"description": "The solo maintainer's GitHub loop: an issue tracker, plan-first pull requests, in-session implementation, review rounds judged by a fresh-context reviewer, and gated squash merges, all through the gh CLI.",
"author": {
"name": "izkreny",
"url": "https://github.com/izkreny"
},
"repository": "https://github.com/izkreny/agentifico",
"license": "MIT",
"keywords": [
"github",
"pull-requests",
"code-review",
"issue-tracker",
"solo-developer",
"gh-cli"
]
}
What it installs
The manifest is a name and a version. 4 skills, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 772 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 20 lines scan A 176a35f421c8
gh-solo is a plugin published in the GitHub repository izkreny/agentifico (2 stars, last pushed 3d 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
git-pr
Committing, PR creation and review triage, and dependency upgrades.
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
palas-git
AI skills for your business and projects that helps you work with git. Includes well-structured commits with conventional format.
2-commit-fast
Automates git commit process by selecting the first suggested message, generating structured commits with consistent formatting while skipping manual confirmation and removing Claude co-Contributorship footer.