Root AGENTS.md
Canonical setup, architecture, workflow, verification, and approval boundaries written for repository-wide agent use.
← WrightOps services
Founding offer · one public repository
Give coding agents consistent repository rules.
One focused pull request. Exactly two repository-specific instruction files, grounded in committed public evidence at one revalidated revision.
$249 USD · One business day after complete
public inputs and provider-confirmed settled payment.
Use the public GitHub form or business email. Never send private or payment data.
Files changed
2/2
- Root agent guidance
- AGENTS.md
- Selected companion
- copilot
- Application-code changes
- 0
- Hosted release check
- passed
public sample wrightops-ai/bounty-red-flag-card#1
Scope
1 public GitHub repository
Diff
Exactly 2 Markdown files
Revision
1 included round
Delivery
1 business day
The exact deliverable
One source of truth, expressed for the agents your team uses.
The contribution is deliberately small enough to review. Unknown procedures stay unknown; public evidence becomes concise, repository-specific operating guidance.
Read the free AGENTS.md vs CLAUDE.md guideRoot
One selected companion
Choose root CLAUDE.md or
.github/copilot-instructions.md during written
scope confirmation—not both.
One reviewable public PR
A pinned two-file diff with its evidence, limitations, acceptance checks, and one revision round within seven days.
-
01
Repository identity
One canonical public GitHub URL and one full default-branch commit SHA define the delivery.
-
02
Contribution workflow
Public contribution guidance, branch rules, review expectations, and ownership boundaries shape the proposed text.
-
03
Architecture and paths
Committed README and architecture material provide the map; undocumented structure is not presented as fact.
-
04
Verification commands
Commands appear only when public source evidence supports them, with no claim that WrightOps executed them.
-
05
Risky-action boundaries
Approval gates, protected systems, secrets, deployment, and destructive actions are named only when evidenced.
Public demand, not testimonials
Four repositories asked for better agent instructions.
WrightOps answered each owner-authored public issue once with a public-read-only preflight pinned to one immutable revision. Scores measure evidenced repository readiness at that snapshot, not code quality or a promised outcome.
-
01
StoneCypher/jssm
Public snapshot
f4f949680/100 Inspect evidence reply -
02
p2well/dotfiles
Public snapshot
04ee3f420/100 Inspect evidence reply -
03
frankxai/creator-intelligence-system
Public snapshot
8e9ad4535/100 Inspect evidence reply -
04
Zugruul/development-skills
Public snapshot
2f3d2f530/100 Inspect evidence reply
These repositories are not customers, paid engagements, testimonials, or endorsements. The linked comments are WrightOps' own public evidence and opt-in scope offers; none created a sale, contract, payment obligation, or guaranteed contribution.
The process
Evidence first. Scope second. Payment third.
-
01
Run the free preflight
Complete the browser-only preflight or automated public audit so the request begins with an immutable evidence baseline.
-
02
Open a non-binding scope request
Name the repository, full revision, selected companion path, public source links, and your authority to receive the proposed contribution. Use the public GitHub form or business email. Never include contact or payment details, credentials, personal or customer data, checkout links, or transaction IDs in either request.
-
03
Receive written scope
WrightOps revalidates the repository and confirms the two paths, price, delivery clock, exclusions, and acceptance shape in writing. After confirmation, email zach@zachwright.xyz to receive a private, buyer-specific PayPal Goods & Services checkout.
-
04
Review the public pull request
Work begins only after provider-confirmed settlement. Delivery is due within one business day after settlement and complete accepted inputs.
The boundary is part of the product
Two files means two files.
“Ready to merge” means a reviewable, bounded proposal. It does not mean owner approval, passing checks, adoption, or a guaranteed merge.
Read scope, credit, revision, and refund terms- ✓ One public repository and revalidated revision
- ✓ Root AGENTS.md plus one selected companion
- ✓ One revision 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 merge, adoption, savings, or outcome guarantee
Before you request scope
Direct answers.
Is a scope request a contract or payment obligation?
No. WrightOps must confirm the exact written scope before privately sharing checkout.
Can I receive both companion files?
No. The fixed offer includes root AGENTS.md and one selected companion: root CLAUDE.md or .github/copilot-instructions.md.
Does WrightOps run the repository's checks?
No. The service reads public evidence and may document supported commands, but it does not clone or execute target code.
Can a prior $149 Fix Plan reduce the price?
A settled Fix Plan for the exact same repository and revision may receive a $149 credit after eligibility review, leaving $100 due.
What happens if WrightOps cannot deliver?
If WrightOps cannot deliver the confirmed scope, you receive a full refund of every dollar paid through the original payment rail.
One repository · two files · one public pull request
Make the repository explain itself before the next agent session.
Use the public scope form or business email. No checkout is shared and no work begins until WrightOps confirms the exact repository, revision, companion, exclusions, and delivery terms in writing. Use GitHub or business email; never send contact or payment details, credentials, personal or customer data, checkout links, or transaction IDs.