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/jerry7991/standup-ghostWrote 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/jerry7991/standup-ghost/standup-ghost)<a href="https://agentmods.dev/plugins/jerry7991/standup-ghost/standup-ghost"><img src="https://agentmods.dev/badge/plugins/jerry7991/standup-ghost/standup-ghost/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/jerry7991/standup-ghost/standup-ghost"><img src="https://agentmods.dev/badge/plugins/jerry7991/standup-ghost/standup-ghost.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
standup-ghost 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": "standup-ghost",
"displayName": "Standup Ghost",
"version": "0.1.3",
"description": "Never write a standup again. Composes and posts your daily standup from what you actually did — Jira, GitHub, Claude Code sessions, Google Calendar — on a schedule, unattended.",
"author": { "name": "Anup Kumar Singh", "url": "https://github.com/jerry7991" },
"homepage": "https://github.com/jerry7991/standup-ghost",
"repository": "https://github.com/jerry7991/standup-ghost",
"license": "MIT",
"keywords": ["standup", "automation", "slack", "jira", "daily-report"]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 312 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.
- 1mo ago First seen · 12 lines scan A 2ebe6cb2d2b2
standup-ghost is a plugin published in the GitHub repository jerry7991/standup-ghost (2 stars, last pushed 13d 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
telegram-topics
Telegram channel for Claude Code — 1 project = 1 forum topic, with a live working/idle status badge on each topic. Run multiple projects concurrently, get notifications, and drive or approve sessions remotely from your phone. Configure with /telegram-topics:configure.
standup
Records what every Claude Code session actually shipped, then renders it as a page you can read before standup.
slopstop
Autonomous, ticket-anchored AI development for GitHub Issues, Linear, and JIRA, built on one idea: stop slop before it goes in, instead of reviewing it out afterwards. Work starts from a ticket, not a prompt. One command drives the whole lifecycle for one ticket or twenty at once, interleaved and unattended…
git-timesheet
Generate weekly timesheets from git commit history. Allocates hours based on commit complexity, supports holidays by country, PTO/sick days, multiple team members, project mapping, custom templates, and saved profiles.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
alibabacloud-spec-ops
Alibaba Cloud AI Ops Plugin - Infrastructure operations workflow with intelligent planning, validation, and execution powered by MCP tooling.