SkillHub is a self-hosted registry where organizations publish, discover, version, and manage reusable skills for AI agents. Teams use it to share governed skill packages privately, with namespaces, role-based access control, audit logs, and CLI installation; the catalogue entries are skills and related agent integrations that can be managed through it.
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/iflytek/skillhub/pr-submissionnpx skills add iflytek/skillhub --skill pr-submissiongit clone --depth 1 https://github.com/iflytek/skillhubWrote 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/iflytek/skillhub/pr-submission)<a href="https://agentmods.dev/skills/iflytek/skillhub/pr-submission"><img src="https://agentmods.dev/badge/skills/iflytek/skillhub/pr-submission.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.00028 | $0.00741 |
| Opus 5 | $0.00014 | $0.00370 |
| Sonnet 5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
pr-submission 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 5d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Submission Skill
Workflow
- Identify the scope of your change (feature, bug fix, docs, test, refactor, chore)
- Format PR title and commits using the conventions below
- Run the pre-PR checklist commands
- Open the PR with a descriptive body
PR Title Format
Use conventional commit style:
<type>(<scope>): <description>
Types:
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
docs |
Documentation changes only |
test |
Adding or updating tests |
refactor |
Code restructuring with no behavior change |
chore |
Build, CI, tooling, or maintenance tasks |
Scopes: Use module or domain names: auth, search, publish, review, namespace, governance, deploy, ci, frontend, scanner
Examples:
feat(auth): add local account login with password reset
fix(publish): resolve null pointer when skill metadata is missing name
docs(deploy): clarify runtime image usage
test(namespace): add membership service edge case tests
refactor(review): extract query repository for governance list
chore(ci): add parallel workflow scripts for multi-agent development
Commit Message Format
Same convention as PR titles. One logical change per commit.
Types:
- feat: A new feature for the user
- fix: A bug fix for the user
- docs: Documentation changes only
- test: Adding or updating tests
- refactor: Code change that neither fixes a bug nor adds a feature
- chore: Changes to build process, CI, or maintenance tasks
Examples:
fix(auth): resolve session cookie conflict in device flow
feat(publish): support security scan before review submission
docs(skill-protocol): add nested SKILL.md discovery rules
test(search): verify jieba analysis with Chinese skill descriptions
refactor(storage): simplify LocalFile path normalization
Pre-PR Checklist
- Backend tests pass:
make test-backend-app - Frontend typecheck passes:
make typecheck-web - If API changed:
make generate-apiwas run andweb/src/api/generated/schema.d.tsis committed - Smoke test passes:
make staging - Follow existing module boundaries and dependency direction
- Add/update tests for new behavior
- Update design docs when APIs, auth flows, deployment, or operator workflows change
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.
- 5d ago First seen · 94 lines · 28 tokens per session scan A b163c20b8338
pr-submission is a skill published in the GitHub repository iflytek/skillhub (5,003 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 741 once invoked, about $0.0001 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-30.
Other skills, from other repositories
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openclaw-docs
Find authoritative guidance for installing, configuring, operating, securing, and troubleshooting OpenClaw, including channels, model providers, Gateway operations, tools, plugins, automation, nodes, multi-agent routing, and CLI errors. Use for any question or maintenance task involving an OpenClaw installation…
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
anysearch
Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction.