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 agentmods add skills/justomsharma/github-resume-assistant/open-prnpx skills add justomsharma/github-resume-assistant --skill open-prgit clone --depth 1 https://github.com/justomsharma/github-resume-assistantWrote 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/justomsharma/github-resume-assistant/open-pr)<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/open-pr"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/open-pr.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00363 |
| Opus 5 | $0.00023 | $0.00181 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
open-pr 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 3d 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.
What it actually says
open-pr
Open a pull request for the pushed branch. Follow docs/GIT_WORKFLOW.md.
Steps
- Confirm the branch is pushed (
git pushdone in/commit-push). - Create the PR with the GitHub CLI:
gh pr create --title "<Conventional Commit summary>" --body "<template below>" - Fill the PR body with the project template:
## What
<one paragraph: what this PR does>
## Why
<link to the ROADMAP item or the reason>
## How
<key implementation choices a reviewer should know>
## Testing
<what tests were added; how you verified it works>
## Checklist
- [ ] Tests pass locally (`pytest`)
- [ ] `ruff` + `mypy` clean
- [ ] No secrets in the diff
- [ ] Docs updated if behavior changed
- [ ] ROADMAP.md item checked off if completed
Guardrails
- Keep PRs small — one ROADMAP item or less. If the branch does more, say so and consider splitting.
- Title = the main Conventional Commit summary.
- If this completes a ROADMAP.md item, update the checkbox in
docs/ROADMAP.mdin the same PR.
Handoff
Once the PR is open → hand off to /review-pr to review it before merging
(yes, review your own PR — see GIT_WORKFLOW.md).
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.
- 3d ago First seen · 52 lines · 47 tokens per session scan A 8d564caefdaa
open-pr is a skill published in the GitHub repository justomsharma/github-resume-assistant (0 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 363 once invoked, about $0.0002 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…