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.
npx skills add lahkiri/xeo-forge --skill connectivity-auditgit clone --depth 1 https://github.com/lahkiri/xeo-forgeWrote 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/skills/lahkiri/xeo-forge/connectivity-audit)<a href="https://agentmods.dev/skills/lahkiri/xeo-forge/connectivity-audit"><img src="https://agentmods.dev/badge/skills/lahkiri/xeo-forge/connectivity-audit/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.
<a href="https://agentmods.dev/skills/lahkiri/xeo-forge/connectivity-audit"><img src="https://agentmods.dev/badge/skills/lahkiri/xeo-forge/connectivity-audit.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00255 |
| Opus 5.5 | $0.00022 | $0.00102 |
| Sonnet 5.5 | $0.00011 | $0.00051 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
connectivity-audit 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 1mo 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.
What it actually says
Before declaring any Xeo Forge feature complete, the agent walks its wiring through four layers and records the evidence for each: the schema (column or table in lib/db/schema.ts), the API surface (a route in app/api that reads or writes it), the runtime (the agent loop or server logic that acts on it), and the UI (a control or display bound to it). A feature missing any layer is reported as a gap with the exact missing layer named, not as complete.
The agent keeps a connectivity table for the release it is building — Feature | schema | API | runtime | UI — and fills every cell with a file reference or an explicit NO. Any row containing NO is either fixed in the same pass or disclosed in README under honest boundaries before the release ships. This skill exists because the v1.21 autonomy feature was wired through two layers while being announced through four; the table method makes that class of failure visible before release, not after.
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.
- 1mo ago First seen · 9 lines · 56 tokens per session scan A 3f411b059a12
connectivity-audit is a skill published in the GitHub repository lahkiri/xeo-forge (11 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 255 once invoked, about $0.0002 per session on Opus 5.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-08-30.
Other skills, from other repositories
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.
understand-issue
Investigate a GitHub issue or reported bug the way a seasoned maintainer would — form an independent model before reading the thread's theories, trace the mechanism and history, verify the diagnosis, and return a concise briefing with a verdict and fix direction. Use for triage, root-cause analysis, or…
triage-issue
First-contact triage for a GitHub issue.
fastgpt-docker-deploy
FastGPT Docker Compose self-hosting deployment workflow. Use when a user asks an AI agent to deploy FastGPT with Docker by referencing /deploy/SKILL.md, including creating an empty fastgpt directory, running the install script in non-interactive mode, starting Docker Compose, monitoring service health, troubleshooting…
gh-bulk-issues
Orchestrate parallel Mastra Code headless instances to debug and fix multiple GitHub issues simultaneously.