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/igptai/skillsWrote 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/igptai/skills/igpt-it)<a href="https://agentmods.dev/plugins/igptai/skills/igpt-it"><img src="https://agentmods.dev/badge/plugins/igptai/skills/igpt-it/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/igptai/skills/igpt-it"><img src="https://agentmods.dev/badge/plugins/igptai/skills/igpt-it.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
igpt-it 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": "igpt-it",
"description": "IT intelligence skills powered by iGPT. Tracks incidents, access requests, software license renewals, security alert signals, change requests, and IT vendor commitments — all automatically from connected email datasources.",
"version": "1.0.0",
"author": { "name": "iGPT AI", "email": "[email protected]", "url": "https://www.igpt.ai" },
"homepage": "https://github.com/igptai/skills/tree/main/plugins/igpt-it",
"repository": "https://github.com/igptai/skills",
"license": "MIT"
}What it installs
The manifest is a name and a version. 6 skills, 1 agent travel with it, and installing the plugin installs all of them — 658 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 · 9 lines scan A 17216daeed4d
igpt-it is a plugin published in the GitHub repository igptai/skills (17 stars, last pushed 5mo 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
pr-workflow
PR and issue lifecycle — structured planning (CEO/Eng gates), PR creation, code review, issue triage, session handoffs.
workflow
Structured development workflow - explore, plan, implement, deliver.
skillry-core-operations
Repo diagnostics and codebase mapping, architecture review and ADRs, specs and implementation planning, refactor safety, diff and regression review, release readiness (deploy preflight, rollback, handoff), and project bootstrap.
roadmap
Product management, roadmap analysis, and solution architecture with multi-agent orchestration.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
giovanni
AI Chief of Staff runtime: 4-layer memory with hard limits, daily digest with drift detection, stakeholder trajectories, invisible shadow hypotheses, adversarial-default review, and a governance lint that fails the build on contradictions. State lives in your repo; the mechanism lives here.