Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ELYRAON Repo Maintainer

    2

    Autonomous repository maintenance that finds actionable engineering work, produces verified fixes, and returns qualified patches with verification reports.

    $149

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned

    About this skill

    ELYRAON Repo Maintainer is a hosted autonomous repository-maintenance service powered by ELYRAON's private NOVA/FETT infrastructure.

    It analyzes an authorized repository, identifies actionable engineering work, implements qualified fixes, runs verification, and returns a verified patch together with a maintenance and verification report.

    The customer receives the maintenance results, not the private NOVA/FETT backend.

    What it does

    • Analyzes an authorized code repository
    • Identifies actionable maintenance work
    • Plans implementation work
    • Produces code changes
    • Runs verification against the repository's test suite
    • Returns a qualified patch/diff
    • Returns findings and a verification report
    • Preserves prior results for later review
    • Supports recurring maintenance runs within the customer's subscription limits

    Current verified scope

    The current 0.1.0 service has been verified end to end on Python repositories using pytest.

    The production flow has been proven through:

    repository authorization → ingestion → planning → dispatch → implementation → verification → patch generation → customer-facing result retrieval

    A full public production canary completed successfully through https://api.elyraon.com.co.

    How it works

    The Agensi skill communicates with the hosted ELYRAON Repo Maintainer API.

    The private NOVA/FETT implementation remains on ELYRAON infrastructure and is not distributed to customers.

    Customers authenticate using an ELYRAON-issued service key.

    Repositories are registered as pinned snapshots. Public repositories can be explicitly refreshed. Private repositories require authorized repository credentials for refresh/access.

    What the customer receives

    • Findings
    • Maintenance-run status
    • Verified code changes
    • Patch/diff output
    • Verification results
    • Maintenance report

    The customer reviews and applies the patch and opens any pull request themselves.

    Current subscription model

    The initial service is intentionally bounded. The backend currently supports:

    • One active customer worker globally at a time
    • Per-tenant usage and repository limits
    • Queued work when capacity is occupied
    • Fail-closed handling when multi-task patches cannot be combined safely

    Capacity limits affect when accepted customer work runs, not whether the internal FETT system changes its eligibility policy.

    Security and isolation

    • Customer API access is tenant-scoped.
    • Service keys are stored only as hashes.
    • Repository credentials are not persisted unnecessarily and are not logged.
    • Cross-tenant repository, run, patch, and verification access has been regression-tested and returns not-found behavior.

    The service does not claim hardened OS-level isolation for arbitrary untrusted repository execution. Customer jobs currently run on ELYRAON's controlled backend infrastructure with the documented service boundary.

    Requirements

    • Active ELYRAON Repo Maintainer subscription
    • ELYRAON-issued service key
    • Repository the customer is authorized to access
    • For private repositories, authorized repository credentials
    • Production API access to https://api.elyraon.com.co

    Verified production checks

    Public TLS, public end-to-end canary, authorization, repository registration, planning, dispatch, implementation, verification, patch retrieval, verification report retrieval, tenant isolation, key rotation/revocation, inactive subscription handling, explicit repository refresh, and queueing under one-worker capacity: all PASS. Two simultaneous public requests were tested; one ran and one queued, then both completed. Current package client tests: 7 passed. Current commercial backend tests: 30 passed.

    Authentication & subscription

    Requires an ELYRAON-issued service key tied to an active Repo Maintainer subscription. In v0.1.0, service keys are provisioned and subscriptions are activated manually by ELYRAON; ELYRAON supplies the service credential after subscription activation. The skill package itself contains no backend access.

    • Version 0.1.0 is currently verified for Python repositories using pytest.
    • The service returns verified patches and reports; it does not open, push, or merge pull requests.
    • Repository registration pins a specific snapshot until explicitly refreshed.
    • Public repositories can refresh without credentials; private repositories require authorized credentials.
    • Fine-grained GitHub-token minimum scope has not yet been independently verified; private-repo access has been verified using an authenticated GitHub credential.
    • Current customer-job concurrency is intentionally limited to one active worker; additional requests may queue until capacity is available.
    • Multi-task patch conflicts fail closed into service review instead of returning an unsafe combined patch.
    • Repositories that track generated files (such as .pyc files) can increase patch-conflict risk.
    • The service does not claim hardened sandbox isolation for arbitrary untrusted repository code.
    • Results are verified against available repository tests; a verified patch is not a guarantee of acceptance, correctness in every environment, or bug-free software.
    • v0.1.0 uses manually provisioned ELYRAON service keys and manually managed subscription activation; ELYRAON supplies the service credential after activation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Com
    Python

    Permissions

    Network Access
    Environment Variables

    Allowed Hosts

    api.elyraon.com.co

    Network Access: Connects to the hosted ELYRAON Repo Maintainer API at api.elyraon.com.co. Environment Variables: Used for the customer's ELYRAON service key and optional API URL override. api.elyraon.com.co: Hosted ELYRAON Repo Maintainer service used for repository-maintenance requests, status, patches, findings, and verification reports. Requires an ELYRAON-issued service key tied to an active Repo Maintainer subscription. Repository analysis, implementation, and verification run on ELYRAON's hosted backend, not in the customer's agent runtime.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    It analyzes an authorized repository, identifies actionable maintenance work, implements qualified fixes, verifies the changes, and returns a patch plus findings and a verification report.

    No. NOVA/FETT remain private ELYRAON backend infrastructure. The Agensi skill connects to the hosted Repo Maintainer service.

    No. Version 0.1.0 returns verified patches and reports. You review and apply the patch and open any pull request yourself.

    No. Work is subject to the customer's plan limits and current service capacity. Work may queue when the active worker is occupied.

    The request queues until customer-worker capacity becomes available. Current production concurrency is intentionally limited to one active customer job.

    Public repositories can be registered and explicitly refreshed without credentials. Private repositories require credentials authorized to read the repository.

    Repo Maintainer runs the repository's supported test/verification workflow and returns the resulting verification status with the patch.

    No. Verification provides evidence that the patch passed the available test workflow, but it does not guarantee acceptance or correctness in every environment.

    The run fails closed into service review rather than returning an unsafe combined patch.

    New maintenance work is disabled while previously generated results remain readable under the current service policy.

    New in Code Quality & Review