platform_management

platform_management is a skill for Claude Code, Codex from ParendumOU/Nexora. It costs 0 tokens per session (686 once invoked), scanned A, original, MIT.

A reference guide for managing a platform made of backend, frontend, proxy, database, and cache services. It documents service names, important paths, and safe restart commands.

In plain words
What is it for?
Use it to inspect service status, find backend and frontend files, identify the API and database-related directories, and restart selected services.
Why use it?
It helps an agent locate code and understand how the platform's services fit together before checking or restarting one.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect service status, find backend and frontend files, identify the API and database-related directories, and restart selected services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parendumou/nexora/platform_management
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 ParendumOU/Nexora --skill platform_management
Clone the repo
git clone --depth 1 https://github.com/ParendumOU/Nexora

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 platform_management

README.md
[![agentmods](https://agentmods.dev/badge/skills/parendumou/nexora/platform_management.svg)](https://agentmods.dev/skills/parendumou/nexora/platform_management)
Your own site
<a href="https://agentmods.dev/skills/parendumou/nexora/platform_management"><img src="https://agentmods.dev/badge/skills/parendumou/nexora/platform_management.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 686 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 31
    Potential security issue detected. Manual review is recommended.
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
How audits are shown
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.00000 $0.00686
Opus 5 $0.00000 $0.00343
Sonnet 5 $0.00000 $0.00137
Haiku 4.5 $0.00000 $0.00069

Measured 8d ago against content hash 8bcc01e8c2d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

platform_management 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 8d 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.

backend/src/seeds/skills/builtin/platform_management/SKILL.md · 75 lines

How it starts

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

Platform Management

Services

Service Filter Role
backend name=backend FastAPI API
frontend name=frontend Next.js UI
nginx name=nginx Reverse proxy
postgres name=postgres PostgreSQL
redis name=redis Cache/pub-sub

File paths (backend container)

Path Contents
/app Backend source root
/app/src/api/routers/ Route handlers
/app/src/models/ SQLAlchemy models
/app/src/skills_data/ Skill seeds
/app/src/main.py Entry point
/workspace-root/AgenticChats/frontend/ Frontend root
/workspace-root/AgenticChats/frontend/src/app/ Next.js routes
/workspace-root/AgenticChats/frontend/src/components/ React components
/workspace-root/AgenticChats/frontend/src/lib/api.ts API client

/workspace-root = volume mount of parent dir.

Restart services

Docker socket at /var/run/docker.sock. Use shell_run.

docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"

# frontend — safe
docker ps --filter "name=frontend" --format "{{.Names}}" | xargs docker restart

# nginx — brief drop
docker ps --filter "name=nginx" --format "{{.Names}}" | xargs docker restart

# backend — drops all WebSocket sessions. Confirm with user first.
docker ps --filter "name=backend" --format "{{.Names}}" | xargs docker restart

Hot-reload

  • Backend (dev): Uvicorn --reload. Any .py save under /app/src/ → auto-reload ~1s.
  • Frontend (dev): Next.js HMR. Any .tsx/.ts/.css save → instant refresh.
  • Production: Restart required after edits.

Logs

docker ps --filter "name=backend" --format "{{.Names}}" | xargs -I{} docker logs --tail 100 {}
docker ps --filter "name=frontend" --format "{{.Names}}" | xargs -I{} docker logs --tail 100 {}
docker ps --filter "name=nginx" --format "{{.Names}}" | xargs -I{} docker logs --tail 20 --follow {}

DB inspection

PGPASSWORD=$POSTGRES_PASSWORD psql -h postgres -U $POSTGRES_USER -d $POSTGRES_DB \
  -c "SELECT id, name, slug FROM organizations ORDER BY created_at;"

Read the full file on GitHub · 75 lines

Files

What ships with it

1 file 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.

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. 8d ago First seen · 75 lines · 0 tokens per session scan A 8bcc01e8c2d1

Subscribe to this mod's changes

platform_management is a skill published in the GitHub repository ParendumOU/Nexora (20 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 686 tokens. 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.

Related

Other skills, from other repositories

agent-tool

Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.

vstorm-co/full-stack-ai-agent-template · 66 tokens

background-task

Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.

vstorm-co/full-stack-ai-agent-template · 62 tokens

rag-knowledge

Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…

vstorm-co/full-stack-ai-agent-template · 76 tokens

alembic-migration

Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.

vstorm-co/full-stack-ai-agent-template · 56 tokens

channel-bot

Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.

vstorm-co/full-stack-ai-agent-template · 53 tokens

frontend-feature

Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.

vstorm-co/full-stack-ai-agent-template · 64 tokens