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/giuseppe-trisciuoglio/developer-kitWrote 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/giuseppe-trisciuoglio/developer-kit/github-spec-kit)<a href="https://agentmods.dev/plugins/giuseppe-trisciuoglio/developer-kit/github-spec-kit"><img src="https://agentmods.dev/badge/plugins/giuseppe-trisciuoglio/developer-kit/github-spec-kit/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/giuseppe-trisciuoglio/developer-kit/github-spec-kit"><img src="https://agentmods.dev/badge/plugins/giuseppe-trisciuoglio/developer-kit/github-spec-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github-spec-kit 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 today.
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-spec-kit",
"version": "4.0.1",
"description": "GitHub specification integration and verification",
"author": {
"name": "Giuseppe Trisciuoglio",
"email": "[email protected]"
},
"homepage": "https://github.com/giuseppe-trisciuoglio/developer-kit",
"repository": "https://github.com/giuseppe-trisciuoglio/developer-kit.git",
"license": "MIT",
"keywords": [
"github",
"specifications",
"integration",
"verification"
],
"agents": [],
"commands": [
"./commands/speckit.check-integration.md",
"./commands/speckit.optimize.md",
"./commands/speckit.verify.md"
],
"skills": []
}
What it installs
The manifest is a name and a version. 3 commands travel with it, and installing the plugin installs all of them — 92 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.
- today First seen · 26 lines scan A bb6c5ae23bbf
github-spec-kit is a plugin published in the GitHub repository giuseppe-trisciuoglio/developer-kit (343 stars, last pushed yesterday), 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-10.
Other plugins, from other repositories
agentic-workflow
Stack-agnostic agent skills for a disciplined, doc-driven feature/issue workflow: design, plan, execute by phases, review, audit, and ship — with a full internal review pack and merge gates.
infoops
Codex and OpenClaw compatible InfoOps skill for turning workstream signals into structured operational awareness and action priorities.
okr
Objectives and Key Results — drafting objectives that aren't disguised metrics, writing outcome-based key results, target calibration, cascading with conflict detection, confidence-based check-ins, and end-of-cycle scoring with retro.
value-realisation
Benefits mapping, baseline-and-accountability discipline, realisation tracking with attribution rigor, at-risk recovery decisions, and post-implementation review — closes the loop from an approved business case to proven delivered value.
pmo
RAID logs, status reporting, steering committee packs, milestone tracking, and decision logs for running a transformation program.
transformation
Digital maturity assessment, Now/Next/Later transformation roadmaps, target operating model design, technology strategy briefs, and transformation business cases.