discord-output-metrics-footer

Install, configure, maintain, or troubleshoot a compact Discord output footer for OpenClaw that shows live context usage, output tokens, Codex quota remaining, model used, and optional subagent token aggregate under each Discord response.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "discord-output-metrics-footer" with this command: npx skills add udaymanish6/discord-output-metrics-footer

Discord Output Metrics Footer

Use this skill when an OpenClaw workspace should show compact runtime metrics under Discord outputs.

Default footer:

_🟢 ↑54k ↓157 · 21%ctx · 5h 89% · kimi-k2.6:cloud_

With subagent aggregate:

_🟢 ↑54k ↓157 · 21%ctx · 5h 89% · openai-codex/gpt-5.5 · sub ↑31k ↓4k_

What it does

  • Adds a Discord delivery-time footer using OpenClaw plugin hooks.
  • Uses llm_output for actual model/token metrics.
  • Uses message_sending to append the footer without adding prompt tokens.
  • Uses live/cached OpenAI Codex OAuth usage for 5h 89%.
  • Uses color status from context usage and quota remaining.
  • Optionally aggregates nearby subagent LLM usage.

Install into an OpenClaw workspace

Copy the bundled extension template:

mkdir -p ~/.openclaw/extensions/discord-output-metrics-footer
cp -R assets/extension-template/* ~/.openclaw/extensions/discord-output-metrics-footer/

Add this plugin config to ~/.openclaw/openclaw.json:

{
  "plugins": {
    "allow": ["discord-output-metrics-footer"],
    "load": {
      "paths": ["~/.openclaw/extensions/discord-output-metrics-footer"]
    },
    "entries": {
      "discord-output-metrics-footer": {
        "enabled": true,
        "config": {
          "cacheMs": 120000,
          "quotaCacheMs": 60000,
          "contextReserveTokens": 40000,
          "appendSubagents": true,
          "disabledConversations": []
        }
      }
    }
  }
}

Then validate and restart:

openclaw config validate
openclaw gateway restart

Channel deployment

The plugin can run for any Discord channel. To disable specific Discord channel IDs, add them to disabledConversations.

Recommended defaults:

  • Enable in active work channels like #general, #coding, #reasoning, and audit channels.
  • Disable in status-only channels like #feed and incident channels like #system if noise matters.

Configuration

Fields:

  • cacheMs: window for matching recent LLM output and subagent output.
  • quotaCacheMs: minimum interval between Codex quota refreshes.
  • contextReserveTokens: safety reserve subtracted from usable context calculations.
  • appendSubagents: append sub ↑x ↓y when nearby subagent usage is detected.
  • disabledConversations: Discord channel IDs where no footer should be appended.

Color status

  • 🟢: context under 50% and quota over 50%.
  • 🟡: context 50-80% or quota 20-50%.
  • 🔴: context over 80% or quota under 20%.

If context and quota disagree, show the worse status.

Guardrails

  • Do not put footer instructions in agent prompts.
  • Do not call an LLM to calculate footer metrics.
  • Do not fetch Codex quota on every message; use cache.
  • Do not show emails, OAuth profile names, token values, API key prefixes, or auth file paths.
  • Do not add the footer when it would exceed Discord's message limit.

Read references/implementation.md before changing the extension code.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

Vnsh Skill

Securely share files using encrypted, expiring vnsh.dev links with the vnsh CLI for uploading and decrypting shared content.

Registry SourceRecently Updated
Coding

Notion

Notion API for creating and managing pages, databases, blocks, relations, rollups, and multi-workspace profiles via the notioncli CLI tool.

Registry SourceRecently Updated
Coding

Lybic Sandbox

Lybic Sandbox is a cloud sandbox built for agents and automation workflows. Think of it as a disposable cloud computer you can spin up on demand. Agents can perform GUI actions like seeing the screen, clicking, typing, and handling pop ups, which makes it a great fit for legacy apps and complex flows where APIs are missing or incomplete. It is designed for control and observability. You can monitor execution in real time, stop it when needed, and use logs and replay to debug, reproduce runs, and evaluate reliability. For long running tasks, iterative experimentation, or sensitive environments, sandboxed execution helps reduce risk and operational overhead.

Registry SourceRecently Updated
1.2K0aenjoy
Coding

Homeassistant Skill

Control Home Assistant devices and automations via REST API. 25 entity domains including lights, climate, locks, presence, weather, calendars, notifications, scripts, and more. Use when the user asks about their smart home, devices, or automations.

Registry SourceRecently Updated
5.1K7anotb