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 VectorPeak/vectorpeak-agent-skills --skill profile-readme-vpgit clone --depth 1 https://github.com/VectorPeak/vectorpeak-agent-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/vectorpeak/vectorpeak-agent-skills/profile-readme-vp)<a href="https://agentmods.dev/skills/vectorpeak/vectorpeak-agent-skills/profile-readme-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/profile-readme-vp/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/vectorpeak/vectorpeak-agent-skills/profile-readme-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/profile-readme-vp.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.00061 | $0.00900 |
| Opus 5.5 | $0.00024 | $0.00360 |
| Sonnet 5.5 | $0.00012 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
profile-readme-vp 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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Profile README VP
Use this skill as a thin operator guide for the remote GitHub Actions workflow that regenerates VectorPeak's profile README. Do not generate the README locally from this skill.
Source of Truth
- Skill repository:
VectorPeak/vectorpeak-agent-skills - Target repository:
VectorPeak/VectorPeak - Default branch:
main - Workflow file:
.github/workflows/update-profile.yml - Workflow name:
Update profile README - Automation branch:
automation/update-profile-readme - Expected PR title when README changes:
chore: update profile README
The README generation, GitHub fact collection, translation, project classification, contribution classification, star formatting, PR override handling, and pull request reuse logic all live in VectorPeak/VectorPeak. Do not copy or recreate that logic in this skill.
Preflight
Confirm GitHub CLI access before triggering:
gh auth status
gh workflow list --repo VectorPeak/VectorPeak
If Update profile README or update-profile.yml is not listed, stop and report that the remote workflow name or file path may have changed.
Manual Trigger
Prefer GitHub CLI when available:
gh workflow run update-profile.yml --repo VectorPeak/VectorPeak --ref main
If using the GitHub web UI:
- Open
VectorPeak/VectorPeak. - Go to
Actions. - Select
Update profile README. - Choose
Run workflow. - Select branch
main. - Start the run.
Verification
After triggering, verify the run instead of assuming success:
gh run list --repo VectorPeak/VectorPeak --workflow update-profile.yml --event workflow_dispatch --limit 5
Watch the selected run:
gh run watch <run-id> --repo VectorPeak/VectorPeak
gh run view <run-id> --repo VectorPeak/VectorPeak --log
Success means:
- The run finishes with
completed/success. - If generated README content changed, the workflow pushes
automation/update-profile-readmeand creates or updates a PR titledchore: update profile README. - If generated content did not change, the workflow exits successfully without opening a noisy PR.
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.
- 2mo ago First seen · 96 lines · 61 tokens per session scan A 839063d4301c
profile-readme-vp is a skill published in the GitHub repository VectorPeak/vectorpeak-agent-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 900 once invoked, about $0.0002 per session on Opus 5.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
Dotfiles
Manage /.zshrc and a chosen set of /.config/ directories (you name them in Config.md) against a private GitHub dotfiles repo. Intents: Push (verify private remote, scan secrets), Pull (clone/diff), Sync, Restore (timestamped backup), Status, Backup (local timestamped copy). Security scan blocks .env, secrets, tokens…
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…