kdense-pi-agent

name

kdense-pi-agent

description

Build with and use Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers/models/settings, creating Pi skills/extensions/packages/themes/prompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation/orchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).

Kdense Pi Agent

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: active
• Source: kdense
• Audit reasons: none
• Upstream license: MIT
• Inventory: ../../inventory.json
• Upstream instructions: ../../../vendor/scientific-agent-skills/skills/pi-agent/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Read the matching inventory record and verify its status, reasons, source path, and pinned revision.
3. Read the upstream instructions only after confirming this record is still active in the current inventory.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.