Borrowing it
Nothing to install: this file belongs to manakuro/asana-clone-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/manakuro/asana-clone-app/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/manakuro/asana-clone-appWrote 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/manakuro/asana-clone-app/pr)<a href="https://agentmods.dev/skills/manakuro/asana-clone-app/pr"><img src="https://agentmods.dev/badge/skills/manakuro/asana-clone-app/pr/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/manakuro/asana-clone-app/pr"><img src="https://agentmods.dev/badge/skills/manakuro/asana-clone-app/pr.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.00798 |
| Opus 5.5 | $0.00010 | $0.00319 |
| Sonnet 5.5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
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 22d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a pull request
Push the current branch to origin (the maintainer's clone or a contributor's fork) and open a PR against main of the upstream repository, with a description that follows .github/PULL_REQUEST_TEMPLATE.md.
Extra notes from the user (may be empty): $ARGUMENTS
1. Find the repositories
git remote -v
- Head (where the branch is pushed): the
originremote,<head-owner>/<head-repo>. - Base (where the PR is opened): the
upstreamremote if there is one (a fork), otherwiseorigin. Call it<base-owner>/<base-repo>and use<base>below for that remote's name.
Read the owners and repo names from the remote URLs ([email protected]:<owner>/<repo>.git or https://github.com/<owner>/<repo>.git). Don't assume a fixed owner.
2. Check the branch
git branch --show-current
git status --short
git fetch <base> main --quiet
git log --oneline <base>/main..HEAD
git diff --stat <base>/main...HEAD
- If the current branch is
main, stop and ask the user for a branch name. Don't push tomain. - If there are uncommitted changes, ask the user whether to commit them first or leave them out.
- If there are no commits ahead of
<base>/main, stop: there is nothing to open a PR for.
3. Write the title and description
Read the branch name, the commit messages and the diff to understand the change.
- Title: Conventional Commits, like the commits in this repo (
feat(core): …,fix(cli): …,docs: …,build: …,ci: …). For a single-commit branch, reuse the commit subject. - Description: fill in every section of
.github/PULL_REQUEST_TEMPLATE.md, keeping its headings and order:- Summary: the purpose of the change in one or two sentences, then a bullet list of the main changes
- Related Issues:
Closes #<n>for issues the branch fixes (from the branch name, commits or the user's notes), otherwiseNone - Testing: what was run (
pnpm lint,pnpm tsc,pnpm test:ci, the playground app, …) and what was checked by hand - Add anything reviewers should know (breaking changes, follow-ups, generated files to skip) at the end of Summary
- Screenshots are not required.
- Don't add the
🤖 Generated with Claude Codefooter or any link to Claude at the end of the description.
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.
- 22d ago First seen · 70 lines · 24 tokens per session scan A ca8c6b3c8cc2
pr is a skill published in the GitHub repository manakuro/asana-clone-app (22 stars, last pushed 22d ago), licensed MIT. It adds 24 tokens to every session and 798 once invoked, about $0.0001 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-10-08.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.