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/GiustoPiedimonte/agentic-engineering-marketplaceWrote 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/giustopiedimonte/agentic-engineering-marketplace/github-keeper)<a href="https://agentmods.dev/plugins/giustopiedimonte/agentic-engineering-marketplace/github-keeper"><img src="https://agentmods.dev/badge/plugins/giustopiedimonte/agentic-engineering-marketplace/github-keeper/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/giustopiedimonte/agentic-engineering-marketplace/github-keeper"><img src="https://agentmods.dev/badge/plugins/giustopiedimonte/agentic-engineering-marketplace/github-keeper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github-keeper 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 1mo 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": "github-keeper",
"version": "0.4.0",
"description": "Make a public GitHub repo well-made and honest. /readme audits and elevates a README — deriving the hero, voice, badges, and sections from the PROJECT's own identity (fidelity gate, propose-and-confirm), with free-form targeted edits; /opensource adds the community-health files, an honest CI gate, and the right repo settings. Honesty-first; confirms outward actions.",
"author": {
"name": "Giusto Piedimonte"
},
"keywords": [
"readme",
"documentation",
"open-source",
"github",
"community-health",
"ci",
"badges",
"public-repo",
"maintenance"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 236 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.
- 1mo ago First seen · 20 lines scan A b3fed2b6fb41
github-keeper is a plugin published in the GitHub repository GiustoPiedimonte/agentic-engineering-marketplace (13 stars, last pushed 21d 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-30.
Other plugins, from other repositories
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
ccf
Claude Context First — a context-first, spec-driven, wave-parallel development workflow. Keeps CLAUDE.md/.claude specs continuously fresh and grounds every design decision in best practices fetched from Context7 and Microsoft Learn.
issue-to-pr
Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session…