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 alivirgo/Major-AI-Skills --skill gpg-signinggit clone --depth 1 https://github.com/alivirgo/Major-AI-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/skills/alivirgo/major-ai-skills/gpg-signing)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/gpg-signing"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/gpg-signing/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/alivirgo/major-ai-skills/gpg-signing"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/gpg-signing.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.00024 | $0.00820 |
| Opus 5 | $0.00012 | $0.00410 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
gpg-signing 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GPG Signing AI Skill Guide
Overview & Engine Architecture
GNU Privacy Guard (GPG) provides OpenPGP keys for signing and encryption. In engineering workflows, the common use is signing git commits and tags so remotes can verify author authenticity. Agents help generate keys safely, configure git, export public keys to GitHub/GitLab, and never paste private key material into chat logs or tickets.
Private key (local / hardware token)
-> gpg signs commit/tag payload
-> Public key on Git forge
-> UI shows Verified
When to use this skill
- Enabling verified commits for a team
- Signing release tags
- Verifying a downloaded artifact signature
- Rotating or revoking a compromised signing key
Operational directives
- Protect private keys with a strong passphrase; prefer hardware tokens when available.
- Never commit private keys,
.gnupgprivate material, or passphrases to git. - Use a dedicated signing subkey when practical; keep certification key offline if policy requires.
- Publish the public key to the forge; set
user.signingkeyandcommit.gpgsign. - If a key is exposed, revoke promptly and replace signing keys in all machines/CI.
Git signing setup
gpg --full-generate-key # choose RSA 4096 or Ed25519 per policy
gpg --list-secret-keys --keyid-format=long
git config --global user.signingkey <KEYID>
git config --global commit.gpgsign true
git config --global tag.gpgsign true
git commit -S -m "Explain why"
git tag -s v1.2.3 -m "Release 1.2.3"
git verify-commit HEAD
git verify-tag v1.2.3
Export / import sketches
gpg --armor --export <KEYID> > pubkey.asc
gpg --armor --export-secret-keys <KEYID> # ONLY to secure backup media - never tickets
Common pitfalls
| Pitfall | Result | Fix |
|---|---|---|
| Email mismatch vs forge account | Unverified commits | Use the same email or add it to the forge + key UID |
| CI signs with shared unprotected key | Weak trust | Use ephemeral OIDC/sigstore where possible, or HSM |
| Lost passphrase, no revocation cert | Unrecoverable trust story | Store revocation certificate offline at key creation |
| Agent prints private key | Compromise | Refuse; rotate if already leaked |
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.
- yesterday Changed · -4 tokens per session ecbd066ccb3d
- 7d ago First seen · 91 lines · 28 tokens per session scan A c7f7f2add37d
gpg-signing is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 820 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
version-control
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.