ODS is a system for turning a PC, Mac, or Linux computer into a private local AI server, meaning a machine that runs models and related AI services itself. It supports local model inference, chat, voice, agents, workflows, document retrieval, search, and image generation. The catalogue includes commands and an instruction for operating or configuring this system.
Borrowing it
Nothing to install: this file belongs to Osmantic/ODS. 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/Osmantic/ODS/main/.github/prompts/issue-to-pr.mdgit clone --depth 1 https://github.com/Osmantic/ODSWrote 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/commands/osmantic/ods/issue-to-pr)<a href="https://agentmods.dev/commands/osmantic/ods/issue-to-pr"><img src="https://agentmods.dev/badge/commands/osmantic/ods/issue-to-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.1 | $0.00000 | $0.00719 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
issue-to-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 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.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue to PR — Autonomous CI Mode
You are running in a CI pipeline. You MUST operate fully autonomously. Do NOT use AskUserQuestion. Do NOT pause for user input.
Rules
- Follow ALL design principles from CLAUDE.md: Let It Crash (primary), KISS, Pure Functions, SOLID
- Keep changes minimal and focused — only implement what the issue requests
- Prefer no change over a wrong change — if the issue is vague, ambiguous, or not actionable, make zero changes
- Do NOT modify protected files:
.github/workflows/*— CI/CD pipelines.env*— environment configurationods/installers/*— core installer libraries and phasesods/ods-cli— main CLI toolods/config/*— backend configuration files
- Do NOT modify unrelated code, design philosophy docs, or import ordering
- Do NOT add unnecessary comments, docstrings, or type annotations to unchanged code
- Do NOT create new files unless absolutely necessary — prefer editing existing files
- Do NOT introduce security vulnerabilities (command injection, XSS, SQL injection, etc.)
- All new Python code must pass
ruff checkandpython -m py_compile - All new shell code must pass
bash -nandshellcheck
Steps
Step 1: Understand the Issue
Read the issue details (appended below). Determine:
- Is this issue actionable with specific, implementable changes?
- Does it describe a bug fix, new feature, or enhancement with enough detail?
- If the issue is too vague (e.g., "make the app better", "improve performance"), make zero changes
Step 2: Explore the Codebase
- Read
CLAUDE.mdfor project structure and conventions - Use Glob and Grep to find the files relevant to the issue
- Read the relevant source files to understand existing patterns and conventions
- Identify the minimal set of files that need changes
Step 3: Implement Changes
- Make targeted edits using the Edit tool (prefer Edit over Write for existing files)
- Follow existing code patterns and conventions in the file you're editing
- After each file edit, validate:
- Python files:
python -m py_compile <file>for syntax,ruff check <file>for linting - Shell files:
bash -n <file>for syntax
- Python files:
- Fix any syntax or lint errors before moving on
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 · 67 lines · 0 tokens per session scan A 1bed595c86c4
issue-to-pr is a command published in the GitHub repository Osmantic/ODS (6,213 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 719 tokens. 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-06.
Other commands, from other repositories
start-development
Start development workflow process in Moira.
review
Review code changes against project conventions.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
code-review
Code review a pull request.
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.