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 tomzx/agents --skill github-post-attributiongit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/github-post-attribution)<a href="https://agentmods.dev/skills/tomzx/agents/github-post-attribution"><img src="https://agentmods.dev/badge/skills/tomzx/agents/github-post-attribution.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 18 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 77 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 103 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00079 | $0.01830 |
| Opus 5 | $0.00039 | $0.00915 |
| Sonnet 5 | $0.00016 | $0.00366 |
| Haiku 4.5 | $0.00008 | $0.00183 |
Grade A, and why
github-post-attribution 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub post attribution (shared)
Skills that post content to GitHub should append a small footer: link to the invoking skill's SKILL.md at the current agents commit (the revision in use when the post was made), plus the model name that executed the skill.
When to use
- Any
ghcommand that creates or updates issue/PR text visible on GitHub. - Invoked by name from other skills (e.g. "follow
skills/github-post-attribution/SKILL.mdbefore posting").
Resolve repository root, commit, and GitHub base URL
REPO_ROOT = the directory that contains skills/ (the agents checkout). The path to this file is always known from the Read call that loaded it. Use it directly -- no additional filesystem exploration needed.
Every skill file lives at <REPO_ROOT>/skills/<SKILL_DIR>/SKILL.md. Resolve symlinks (e.g. ~/.agents/skills → ~/src/agents/skills) and capture all values in one call:
SKILL_MD_DIR=$(dirname "$(readlink -f /path/to/this/SKILL.md)")
REPO_ROOT=$(cd "$SKILL_MD_DIR" && git rev-parse --show-toplevel)
SKILL_COMMIT=$(cd "$REPO_ROOT" && git rev-parse HEAD)
SKILL_SHORT_SHA=${SKILL_COMMIT:0:7}
REMOTE_URL=$(cd "$REPO_ROOT" && git remote get-url origin)
Replace /path/to/this/SKILL.md with the absolute path used in the Read call. readlink -f resolves any symlinks before git sees the path, so --show-toplevel always returns the real repo root.
From REMOTE_URL, normalize to https://github.com/{owner}/{repo}:
[email protected]:owner/repo.git→https://github.com/owner/repohttps://github.com/owner/repo.git→https://github.com/owner/repo
Call that {BASE}.
Resolve model name
The model that executed the skill is identified by its short name (e.g. glm-5.1, claude-sonnet-4-20250514). The agent knows its own model at runtime from its environment. Set MODEL_NAME to the model's human-facing label:
MODEL_NAME="glm-5.1" # replace with the actual model name at runtime
Link to the invoking skill's file
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.
- 4d ago First seen · 134 lines · 79 tokens per session scan A 65d34961e002
github-post-attribution is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 79 tokens to every session and 1,830 once invoked, about $0.0004 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-03.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…