Nexent is a zero-code platform for creating AI agents from natural-language instructions, combining tools, skills, memory, orchestration, constraints, feedback loops, and control planes. It is intended for people who need to build and deploy agents without writing orchestration code. The catalogue entries are rules and skills for working with Nexent.
Borrowing it
Nothing to install: this file belongs to ModelEngine-Group/nexent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ModelEngine-Group/nexent/develop/.agents/skills/nexent-spec-coding/SKILL.mdgit clone --depth 1 https://github.com/ModelEngine-Group/nexentWrote 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/modelengine-group/nexent/nexent-spec-coding)<a href="https://agentmods.dev/skills/modelengine-group/nexent/nexent-spec-coding"><img src="https://agentmods.dev/badge/skills/modelengine-group/nexent/nexent-spec-coding/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/modelengine-group/nexent/nexent-spec-coding"><img src="https://agentmods.dev/badge/skills/modelengine-group/nexent/nexent-spec-coding.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.00065 | $0.02326 |
| Opus 5.5 | $0.00026 | $0.00930 |
| Sonnet 5.5 | $0.00013 | $0.00465 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
nexent-spec-coding 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexent SPEC Coding
Develop Nexent from an evidence-backed SPEC while keeping product behavior, formal D1-D5 test assets, implementation, and verification synchronized.
Repository boundaries
- Treat
nexent/as the Git-managed product repository and its siblingnexent-doc/as the document repository. - Never run Git commands in the document repository or move SPEC documents into the product repository.
- Preserve unrelated changes. Record the initial branch/status, applicable repository instructions, build configuration, and test layout.
- Keep the existing tests under
test/backend,test/sdk, andtest/ext_componentsas Legacy UT. Do not map them into the formal D1-D5 registry. - Traditional UT is a permanently maintained PR obligation, not a temporary baseline. Assess it for every product-code change, using nexent-python-tests. Preserve all existing D1 Cases/scripts; new D1 focuses on component evidence beyond UT, while D3 proves actual runtime integration. Do not force new Cases at all five stages.
Read the right references
| Work | Required reference |
|---|---|
| Choose the SPEC maintenance mode | spec-maintenance-guide.md |
| Fix a bug with or without an existing SPEC | spec-maintenance-guide.md, bugfix-design-template.md, and nexent-test-assets's bugfix reference |
Create or revise proposal.md |
proposal-template.md |
Create or revise design.md; design formal D1-D5 cases |
design-template.md and test-design-guide.md |
Create or revise task.md |
task-template.md |
| Plan, execute, or close verification | verification-guide.md |
| Add missing tests after product code is already complete | nexent-test-assets's test-backfill.md and test-design-guide.md |
What ships with it
7 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.
- 5d ago Changed · +2 lines b47eaef6cdd0
- 16d ago Changed · +19 lines · +2 tokens per session d9ea39999b56
- 1mo ago Changed · -6 lines · -7 tokens per session 9822ff870de7
- 1mo ago First seen · 74 lines · 70 tokens per session scan A f913dac60b57
nexent-spec-coding is a skill published in the GitHub repository ModelEngine-Group/nexent (6,064 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 2,326 once invoked, about $0.0003 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-09-15.
Other skills, from other repositories
skillsafe-scanner
Run the skillsafe scan on the adamoutler/joplin-server-vector-memory package, then operate and improve/complete all issues identified. Use this when asked to scan or fix skillsafe issues.
joplin-mcp-architecture
Architectural flow and state machine for Joplin MCP Server.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
github-deep-research
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams.…
claude-to-deerflow
Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to…
video-generation
Use this skill when the user requests to generate, create, or imagine videos. Supports structured prompts and reference image for guided generation.