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/martinkuhne/devstack/gitea-prnpx skills add MartinKuhne/devstack --skill gitea-prgit clone --depth 1 https://github.com/MartinKuhne/devstackWhat 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.00022 | $0.01046 |
| Opus 5 | $0.00011 | $0.00523 |
| Sonnet 5 | $0.00004 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
gitea-pr scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls" \ How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide guidance for creating and managing pull requests on Gitea, including:
- Creating pull requests with proper descriptions
- Updating PR status
- Adding reviewers
- Managing PR labels
- Handling PR reviews
Gitea API Reference
Base URL: {GITEA_URL}/api/v1
Authentication: Authorization: token {GITEA_API_TOKEN}
Create Pull Request
curl -X POST "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls" \
-H "Authorization: token {GITEA_API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"title": "feat(auth): add OAuth2 support",
"body": "## Summary\n\nThis PR adds OAuth2 authentication.\n\n## Changes\n- Add Google OAuth2 provider\n- Implement token refresh",
"head": "feature/123-oauth2",
"base": "main"
}'
Get Pull Request
curl "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls/{pr_number}" \
-H "Authorization: token {GITEA_API_TOKEN}"
List Pull Requests
curl "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls?state=open&limit=50" \
-H "Authorization: token {GITEA_API_TOKEN}"
Update Pull Request
curl -X PATCH "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls/{pr_number}" \
-H "Authorization: token {GITEA_API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"title": "Updated title",
"body": "Updated description"
}'
Add Reviewers
curl -X POST "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls/{pr_number}/requested_reviewers" \
-H "Authorization: token {GITEA_API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{"reviewers": ["username1", "username2"]}'
Merge Pull Request
curl -X POST "{GITEA_URL}/api/v1/repos/{owner}/{repo}/pulls/{pr_number}/merge" \
-H "Authorization: token {GITEA_API_TOKEN}" \
-H "Content-Type: application/json" \
-d '{"merge_when_all_successful": true}'
Pull Request Template
Use this structure for PR descriptions:
## Summary
Brief description of changes (1-3 sentences).
## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update
## Changes
- Change 1
- Change 2
- Change 3
## Testing
Describe testing performed.
## Screenshots (if applicable)
## Related Issues
Closes #123
Fixes #456
## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Tests added/updated
- [ ] Documentation updated
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.
- yesterday First seen · 166 lines · 22 tokens per session scan A d802cf55c7f9
gitea-pr is a skill published in the GitHub repository MartinKuhne/devstack (2 stars, last pushed 21d ago), licensed MIT. It adds 22 tokens to every session and 1,046 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…