client-orgo-provisioning

client-orgo-provisioning is a skill for Claude Code, Codex from S3YED/appie-kit. It costs 31 tokens per session (2,429 once invoked), scanned A, original, MIT.

A setup procedure for creating a Weblyfe client bot on an Orgo-managed machine, connecting it to Hermes Agent and Telegram, and granting it GitHub access.

In plain words
What is it for?
It helps provision a new client bot from scratch and check an existing bot's Orgo setup.
Why use it?
It removes the repeated manual work of preparing a separate machine, agent, messaging connection, and deployment credentials for each new client bot.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for hermes-agent. Also seen: built for hermes-agent.

Good fit It helps provision a new client bot from scratch and check an existing bot's Orgo setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/s3yed/appie-kit/client-orgo-provisioning
Install

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.

Any agent
npx skills add S3YED/appie-kit --skill client-orgo-provisioning
Clone the repo
git clone --depth 1 https://github.com/S3YED/appie-kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for client-orgo-provisioning

README.md
[![agentmods](https://agentmods.dev/badge/skills/s3yed/appie-kit/client-orgo-provisioning/github.svg)](https://agentmods.dev/skills/s3yed/appie-kit/client-orgo-provisioning)
Your own site
<a href="https://agentmods.dev/skills/s3yed/appie-kit/client-orgo-provisioning"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/client-orgo-provisioning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for client-orgo-provisioning

Your own site · 80×15
<a href="https://agentmods.dev/skills/s3yed/appie-kit/client-orgo-provisioning"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/client-orgo-provisioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.02429
Opus 5 $0.00015 $0.01215
Sonnet 5 $0.00006 $0.00486
Haiku 4.5 $0.00003 $0.00243

Measured 7d ago against content hash 0d46adb9347a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

client-orgo-provisioning 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 7d ago.

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.

skills/client/client-orgo-provisioning/SKILL.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Client Orgo Provisioning

End-to-end provisioning of a Weblyfe client bot on an Orgo-managed machine with Hermes Agent, Telegram gateway, and GitHub deploy access.

Triggers

  • "Set up [client name]'s bot"
  • "Provision [client] on Orgo"
  • "Check [client]'s orgo bot"
  • Any new Weblyfe client needs their own Hermes agent

Prerequisites

Before starting, gather ALL secrets. Use a dedicated Python script that reads from all relevant env files:

secrets = {}
for env_file in ["~/.weblyfe-secrets/.env",
                  "~/.weblyfe-secrets/orgo-openrouter-keys.env",
                  "~/.weblyfe-secrets/bot-provisioning-pool.env"]:
    path = os.path.expanduser(env_file)
    if os.path.exists(path):
        with open(path) as f:
            for line in f:
                line = line.strip()
                if line and not line.startswith('#'):
                    # Handle 'export KEY="value"' format
                    if line.startswith('export '):
                        line = line[7:]
                    if '=' in line:
                        k, v = line.split('=', 1)
                        v = v.strip().strip('"').strip("'")
                        secrets[k.strip()] = v

Key sources:

  • Master Orgo API key: ORGO_API_KEY from ~/.weblyfe-secrets/.env (uses export prefix)
  • Client Orgo API key: ORGO_APPIE<N>_<NAME> from ~/.weblyfe-secrets/orgo-openrouter-keys.env
  • Client Telegram bot token: BOT_APPIE<N>_TOKEN from ~/.weblyfe-secrets/bot-provisioning-pool.env
  • OpenRouter API key: OPENROUTER_API_KEY from ~/.weblyfe-secrets/.env (uses export prefix)
  • Vercel token if needed: VERCEL_TOKEN from ~/.weblyfe-secrets/.env
  • Bot assignment mapping: ~/.weblyfe-secrets/bot-provisioning-ledger.json

Workflow

1. Discover the Orgo computer

Orgo computer IDs are NOT stable across rebuilds. If a previous session had an ID, it's likely stale.

# First, list projects to find the client project
python3.11 -c "
import urllib.request, json, os
# Read master key
with open(os.path.expanduser('~/.weblyfe-secrets/.env')) as f:
    for line in f:
        if line.startswith('export ORGO_API_KEY='):
            key = line.split('=',1)[1].strip().strip('\"').strip(\"'\")
            break
# GET projects
req = urllib.request.Request('https://www.orgo.ai/api/projects', headers={
    'Authorization': f'Bearer {key}', 'Content-Type': 'application/json'})
with urllib.request.urlopen(req) as r:
    print(json.dumps(json.loads(r.read()), indent=2))
"

Read the full file on GitHub · 261 lines

Changes

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.

  1. 7d ago First seen · 261 lines · 31 tokens per session scan F 0d46adb9347a

Subscribe to this mod's changes

client-orgo-provisioning is a skill published in the GitHub repository S3YED/appie-kit (9 stars, last pushed 15d ago), licensed MIT. It adds 31 tokens to every session and 2,429 once invoked, about $0.0002 per session on Opus 5. 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-03.