Complete replacement Markdown
A corrected version of one existing root
AGENTS.md, root CLAUDE.md,
.github/copilot-instructions.md, or
skill/SKILL.md.
← WrightOps services
$149 fixed scope · one public repository
Correct one agent-instructions file without widening the diff.
One existing AGENTS.md, CLAUDE.md,
Copilot instructions, or skill/SKILL.md file becomes
a review-ready correction pack grounded in committed public
evidence.
Build the $149 scope
Choose the right instruction file
Inspect the complete one-file sample
Received this proposal? Verify it
$149 USD · One business day after complete
public inputs and provider-confirmed settled payment.
Written scope comes first. No public checkout or payment
obligation.
Files in scope
1/1
- Existing instruction file
- selected
- Replacement Markdown
- included
- Unified diff
- included
- Application-code changes
- 0
one public revision · maximum 250 source lines
Price
$149 fixed scope
File
1 existing instruction file
Evidence
1 public revision
Delivery
1 business day
No account required
Build the exact $149 request here.
Add one public repository, one existing instructions file, and the factual correction you need. URL shape is checked locally; WrightOps verifies public access after receipt and enforces the 250-line cap.
- ✓ Nothing is uploaded or stored
- ✓ No checkout or payment obligation
- ✓ No repository mutation or code execution
- ✓ Public request, email, and copy paths available
Never include credentials, payment details, private files, personal or customer data, production access, security work, or regulated work. A GitHub request is public. GitHub account required. This builder creates only a non-binding request.
The exact deliverable
A correction pack your maintainer can review before applying.
The result is patch-shaped and evidence-linked. WrightOps does not need a buyer-repository login or write credential.
Ready-to-apply unified diff
One bounded patch for review. No branch, pull request, comment, merge, or repository mutation is included.
Evidence and acceptance checks
Claim-to-source notes, explicit limitations, and factual checks for the maintainer who applies the patch.
-
01
Stale command or path
The existing file points agents at a command, directory, or entry point that public source no longer supports.
-
02
Missing operational boundary
A narrow approval gate, ownership rule, or verification requirement is absent or misleading.
-
03
Conflicting repository guidance
The selected file contradicts committed contribution, architecture, or workflow evidence.
-
04
Product guidance mixed with development notes
The file combines durable repository guidance with changelog-like narrative, temporary implementation notes, or owner-specific diary entries.
-
05
One-file correction—not a rebuild
The file already exists and the correction fits within 250 source lines and 75 total WrightOps labor minutes.
The process
Evidence first. Scope second. Payment third.
-
01
Prepare public scope
Use the browser-local builder to name the public repository, accepted revision, selected file, correction need, and your authority to commission the work.
-
02
Receive written confirmation
WrightOps confirms the path, price, delivery clock, labor cap, exclusions, and acceptance shape before sharing checkout.
-
03
Settle through PayPal Business
A private, buyer-specific PayPal Goods & Services checkout is provided only after scope confirmation. Work starts after provider-confirmed settlement.
-
04
Review the correction pack
Receive replacement Markdown, a unified diff, evidence notes, and acceptance checks within one business day after settled payment and complete accepted inputs.
The boundary is part of the product
One file means one file.
The $149 tier covers one existing instruction file, no more than 250 source lines, and no more than 75 total WrightOps labor minutes. It includes one factual correction round requested within seven days.
If WrightOps cannot deliver the confirmed scope, every dollar paid is refunded through the original payment rail; any retained seller fee is WrightOps’ cost.
- ✓ One public repository and one revalidated revision
- ✓ One existing instruction file
- ✓ Replacement Markdown, unified diff, evidence, and checks
- ✓ One factual correction round in the same scope
- × No source, CI, test, dependency, or config changes
- × No private code, credentials, or production access
- × No repository code execution or security work
- × No branch, pull request, merge, adoption, or outcome guarantee
One repository · one file · one correction pack
Make the file accurate before the next agent session.
The linked builder runs locally in your browser and prepares a reviewable business-email request. It uploads and stores nothing, creates no checkout, and creates no obligation.