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 jqaisystems/jqai-ai-skills --skill github-profile-proof-updatergit clone --depth 1 https://github.com/jqaisystems/jqai-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/jqaisystems/jqai-ai-skills/github-profile-proof-updater)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/github-profile-proof-updater"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/github-profile-proof-updater/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/jqaisystems/jqai-ai-skills/github-profile-proof-updater"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/github-profile-proof-updater.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.00063 | $0.00690 |
| Opus 5 | $0.00032 | $0.00345 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
github-profile-proof-updater 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Profile Proof Updater
Overview
Use this skill to turn a GitHub profile or proof-layer refresh into a repeatable, public-safe workflow: update visuals, preserve working README paths, verify the live page, and create the social/proof trail that explains the update.
Do not publish, commit, push, upload, or post externally unless the user explicitly asks for that action.
Workflow
- Confirm the target repo and the source asset folder.
- Inspect the current repo state:
git status --short- README image references
- target asset filenames and dimensions
- Preserve existing public paths unless the user asks for a rename in README.
- Prefer replacing assets under the old filenames.
- Keep known-good hero images unchanged when the user says the hero is already good.
- Copy or replace only the intended assets.
- Validate the changed media:
- destination files exist
- images are readable
- dimensions/aspect ratios are plausible for the README layout
- Re-check README references.
- Edit README only if an image path is broken, missing, or intentionally changing.
- Review the diff and repo status.
- Never use broad staging until the changed files are understood.
- Prefer staging named files only.
- If the user asks to commit/push, commit with a focused message and push the current branch.
- Verify the live GitHub profile or public repo page after push.
- Check that all updated visuals render.
- Confirm the unchanged hero remains correct.
- Capture any broken image, stale cache, or layout issue.
- Create or update the proof trail:
- public GitHub links
- commit links or hashes
- asset summary
- LinkedIn/X post links when available
- follow-up checklist
Public Safety Rules
- Do not include local machine paths, private vault structure, raw prompts, logs, credentials, browser cookies, private repo names, account identifiers, or client data in public files.
- Screenshots must not reveal private tabs, emails, analytics, billing, dashboards, file paths, or account menus.
- Social copy should describe outcomes and workflow categories, not private implementation details.
- If a public artifact is being prepared, apply the
github-safe-publisherrules and run its scanner when available.
What ships with it
1 file beside SKILL.md 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.
- 11d ago First seen · 74 lines · 63 tokens per session scan A f478d6ed75b3
github-profile-proof-updater is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 690 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-31.
Other skills, from other repositories
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
create-pr
Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a pull request", "open a PR", or "submit a PR".