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.
npx skills add sgaunet/claude-plugins --skill upd-project-descriptiongit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/skills/sgaunet/claude-plugins/upd-project-description)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/upd-project-description"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/upd-project-description/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/skills/sgaunet/claude-plugins/upd-project-description"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/upd-project-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.01184 |
| Opus 5.5 | $0.00009 | $0.00474 |
| Sonnet 5.5 | $0.00004 | $0.00237 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade B, and why
upd-project-description scanned grade B with 2 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 22d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
`curl -X PATCH -H "Authorization: token <TOKEN>" -H "Content-Type: application/json" -d '{"description":"<description>"}' <api_base>/repos/<owner>/<repo>` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Skill, Bash(gh:*), Bash(glab:*), Bash(fgj:*), Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Project Description
Update the description and topics of the current project. This skill automatically detects whether the repository is hosted on GitHub, GitLab, or Forgejo and uses the appropriate CLI (or REST API for Forgejo) to update the project metadata (description and topics/tags).
Process
-
Detect Repository Host: Use the
detect-repo-hostskill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details. -
Analyze README: Use a Haiku agent to analyze the README.md file:
- Extract concise project description (first 1-2 paragraphs, max 200 chars)
- Identify relevant topics/tags from content (technologies, frameworks, keywords)
- Return:
{description: "...", topics: ["topic1", "topic2", ...]}
-
Launch 2 parallel Haiku agents to update project metadata concurrently:
Agent #1: Update Project Description
-
GitHub:
gh repo edit --description "<description>" -
GitLab:
glab repo edit --description "<description>" -
Forgejo:
fgjhas norepo editsubcommand — call the Forgejo REST API withcurl, using the token fromfgj auth token:curl -X PATCH -H "Authorization: token <TOKEN>" -H "Content-Type: application/json" -d '{"description":"<description>"}' <api_base>/repos/<owner>/<repo><api_base>is the field returned by thedetect-repo-hostskill (e.g.https://git.sylvlab.fr/api/v1). Never hardcode a host. -
Return: success/failure status
Agent #2: Update Project Topics/Tags
- GitHub:
gh repo edit --add-topic "<topic>"(one per topic) - GitLab:
glab repo edit --tag "<topic>"(one per topic) - Forgejo:
fgjhas norepo editsubcommand — call the Forgejo REST API withcurl, using the token fromfgj auth token(sets the full topic list in one call):curl -X PUT -H "Authorization: token <TOKEN>" -H "Content-Type: application/json" -d '{"topics":["<topic1>","<topic2>"]}' <api_base>/repos/<owner>/<repo>/topics - Return: success/failure status
-
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.
- 22d ago First seen · 75 lines · 22 tokens per session scan B 0b428ce44786
upd-project-description is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 1,184 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other skills, from other repositories
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
review-pr
Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
creating-pr-from-branch
Create a pull request from the current branch. Analyzes commits, generates title+body from PR template, pauses for approval, then pushes and creates PR. Use after committing changes.