Generic template repository and npm CLI scaffold for agentic development environments.
Consolidate best practices from multiple internal agentic repositories into one reusable bootstrap tool.
Implemented as CLI package:
- package:
@klever/agentic-environment - bin:
klever
Install style:
npm install -g @klever/agentic-environment# create a fresh environment
klever init <target-dir> --profile foundation
# wrap an existing repository
klever wrap <target-dir> --profile full
# inspect workspace and generate scan artifacts
klever scan . --scan-executor auto --scan-method deep
# clone and register external source repository
klever add https://github.com/your-org/your-repo.git
# optional: full history clone
klever add https://github.com/your-org/your-repo.git --full-history
# list suggested addons for current workspace
klever addons list .
# install addon package into internal toolkit
klever addons install klever-addon-odoo-business-model .
# execute installed addon against workspace context
klever addons run klever-addon-odoo-business-model . --repo odooklever add clones repositories into repositories/<repo-name> and updates context-engineering/sources/catalog.yaml.
klever scan now:
- detects local coding agents (
codex,copilot,claude,gemini) and allows delegating scan execution - falls back to
llm-apimode when delegation is not selected - generates deep artifacts under
context-engineering/sources/repositories/:source-map.jsonmcp-suggestions.jsonmcp-suggestions.md<repo>.intelligence.json<repo>.intelligence.mdintelligence-index.json
- generates cross-repository topology under
context-engineering/sources/:system-map.jsonsystem-map.md
- generates addon recommendations for second-row context engineering:
addon-suggestions.jsonaddon-suggestions.md
- writes delegated scan prompt (when local agent mode is selected):
context-engineering/scan/delegated-scan-request.md
klever addons install installs npm addon packages into .klever/toolkit/ inside the workspace and tracks them in .klever/toolkit/addons.json.
klever addons run executes installed addon binaries through the toolkit (npm exec --prefix .klever/toolkit ...).
Initialization asks for your LLM provider/API key (openai, anthropic, or gemini) and keeps the key in runtime memory/environment only. It is not persisted to scaffold files.
-
foundation- AGENTS governance
- playbooks
- handoffs
- safety boundaries
- issue/PR intake templates
- preflight + basic validation scripts
- KPI/sprint snapshots
-
context-ops- extends foundation
- source catalog (
context-engineering/sources/catalog.yaml) - context source inventory + ownership templates
- context snapshot schema
- collectors: code, environment, infrastructure, aws, grafana, network
- LLM knowledge builder:
scripts/context/build_knowledge_layer.mjs - redaction library
- freshness + required-domain validation gates
- scheduled context refresh workflow
-
full- extends context-ops
- trusted-source policy for MCP/skills
- MCP client setup docs/config
- skills catalog lifecycle templates
- action gate/guardrail docs
The most important reusable capability in this scaffold is context engineering:
- domain-based context model and source registry
- deterministic collection and validation
- security/redaction policy built into collectors
- ownership and freshness operationalized via workflow + runbooks
docs/capability-matrix.mddocs/context-engineering-findings.mddocs/architecture.mddocs/versioning-policy.mdCHANGELOG.md
npm test- Current release line:
v0.3.0 - Changelog:
CHANGELOG.md - License:
LICENSE
- Contribution guide:
CONTRIBUTING.md - Code of conduct:
CODE_OF_CONDUCT.md - Security policy:
SECURITY.md