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 DemonDamon/AgenticX --skill agenticx-agent-obsgit clone --depth 1 https://github.com/DemonDamon/AgenticXWrote 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/demondamon/agenticx/agenticx-agent-obs)<a href="https://agentmods.dev/skills/demondamon/agenticx/agenticx-agent-obs"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/agenticx-agent-obs/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/demondamon/agenticx/agenticx-agent-obs"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/agenticx-agent-obs.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.00089 | $0.01091 |
| Opus 5.5 | $0.00036 | $0.00436 |
| Sonnet 5.5 | $0.00018 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
agenticx-agent-obs 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticX Observability Assistant (agenticx-agent-obs)
Guide for connecting AI agents to the AgenticX Runtime Observability center (/ops/logs: Overview, Traces, Observations, Sessions) and diagnosing trace errors or latency bottlenecks.
Core Capabilities
- Desktop & Local Runtime Auto-Onboarding: Configure
~/.agenticx/config.yamlso Near desktop sessions automatically reportrun,model,tool, andsubagentspans (including reasoning thought previews) to the enterprise observability endpoint. - Multi-Framework SDK Instrumentation: Instrument Python (
agenticx,openai,langchain,langgraph), TypeScript/Node.js, or Go services to report structured trace spans. - Interactive Trace & Session Diagnosis: Query recent traces, inspect failed
tool/model/subagentobservations, and summarize latency P50/P90 or token spikes using the bundled diagnostic script.
Workflow 1 — Connect Near Desktop to Enterprise Observability
When the user wants their local Near desktop runs to appear in the Enterprise Admin Console (运行观测):
- Inspect
~/.agenticx/config.yamlunder theenterprise:section. - Ensure the following keys are present (ask the user for
base_urlandtokenonly if missing):
(The personal access credential is configured in Near Desktop Settings → Enterprise Connection.)enterprise: enabled: true base_url: "<ENTERPRISE_PORTAL_URL>" user_email: "<USER_ACCOUNT>" - Verify connectivity using the bundled diagnostic script (see Workflow 3).
- Explain privacy guarantees:
- Uploaded spans include
trace_id,step_no,step_kind(run|model|tool|subagent),status,model,provider, token counts,duration_ms, and 500-char clipped previews of user input, assistant reply, and model reasoning (metadata.thought). - Tool arguments and raw tool outputs are never uploaded.
- Uploaded spans include
Workflow 2 — Instrument External Agent Code (Python / LangChain / OpenAI / TS)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 67 lines · 89 tokens per session scan A 9d2cc56cc76d
agenticx-agent-obs is a skill published in the GitHub repository DemonDamon/AgenticX (460 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 1,091 once invoked, about $0.0004 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-10-17.
Other skills, from other repositories
continuum-observability
Trace agent runs with Langfuse, decorate functions with @observe, collect latency/token/error metrics, and report errors. Invoke when the user asks about "see what the LLM was prompted with", "Langfuse traces", "track latency", "metrics dashboard", "error reporting", or "instrument my function".
weather
Get current weather and forecasts.
github
Manage GitHub issues and pull requests, inspect CI runs, and query repository data.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…