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 pPrecel/pkup-gen --skill pkup-enchantgit clone --depth 1 https://github.com/pPrecel/pkup-genWrote 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/pprecel/pkup-gen/pkup-enchant)<a href="https://agentmods.dev/skills/pprecel/pkup-gen/pkup-enchant"><img src="https://agentmods.dev/badge/skills/pprecel/pkup-gen/pkup-enchant/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/pprecel/pkup-gen/pkup-enchant"><img src="https://agentmods.dev/badge/skills/pprecel/pkup-gen/pkup-enchant.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.00059 | $0.04433 |
| Opus 5 | $0.00030 | $0.02217 |
| Sonnet 5 | $0.00012 | $0.00887 |
| Haiku 4.5 | $0.00006 | $0.00443 |
Grade A, and why
pkup-enchant 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enrich an existing PKUP report.
What this skill does
Starting from an already-generated output directory (containing .diff files and a report file), this skill:
- Determines which GitHub providers are needed based on diff filenames
- Verifies
ghCLI login status for those providers - Fetches PR/issue context from GitHub for all commits
- Groups commits into tasks (by linked issue, theme, or repository)
- Presents the grouped tasks for classification and lets you approve which groups to keep
- Removes excluded diffs and their entries from the report
- Writes one-sentence Polish descriptions per group
- Applies the enriched result block directly to the original report file (
.txtor.docx)
Step 0: Determine the report directory
Use the following decision tree:
- Check whether a
reports/subdirectory exists in the current working directory and contains at least one subdirectory with.difffiles:ls reports/ - If
reports/exists and has subdirectories with.difffiles — ask (AskUserQuestion) which subdirectory to use, listing each as an option plus "Custom path" as a fallback. - If
reports/does not exist or has no.difffiles — check whether the current working directory itself contains.difffiles:- If yes — set CWD as outputDir directly, without asking.
- If no — ask the user for the path (AskUserQuestion with a free-text "Custom path" option).
The selected directory must contain at least one .diff file and one report file (*.txt or *.docx). If a report file is missing, continue — pkup-enchant will create a minimal report.txt before writing the final result.
Remember the path as outputDir.
Step 1: Determine required providers and verify login
Scan all .diff filenames in outputDir and derive required providers:
- Filename starting with
kyma-project_→ requires github.com - Filename starting with
kyma_→ requires github.tools.sap - Any other prefix → ask the user which provider hosts that repository
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.
- 11d ago First seen · 372 lines · 59 tokens per session scan A 638035e1d5d6
pkup-enchant is a skill published in the GitHub repository pPrecel/pkup-gen (11 stars, last pushed 28d ago), licensed MIT. It adds 59 tokens to every session and 4,433 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
gh-attach
Uploads a local file (screenshot, image, PDF, zip, video) to GitHub user-attachments, downloads GitHub user-attachments, and embeds local files in a PR, issue, or comment. Use when asked to "attach a screenshot to the PR", "add an image to the issue", "embed before/after screenshots", "attach this file", or "download…
gh-infra
Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.
repository-manifest
Complete YAML schema reference for Repository and RepositorySet resources. Use when writing or editing manifests for repo settings, labels, actions, branch protection, rulesets, secrets, variables, or repository defaults.
file-manifest
Complete YAML schema reference for File and FileSet resources. Use when writing manifests to manage files (CODEOWNERS, LICENSE, CI workflows, etc.) in one or more repositories, including templating, patches, reconcile modes, delivery method, and import-into behavior.
import-into
Use when pulling live GitHub state back into existing gh-infra manifests with gh infra import --into, especially for write/patch/skip decisions, shared file sources, template-backed files, and import safety rules.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.