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.
npx agentmods add skills/jovandyaz/knowtis-app/deployingnpx skills add jovandyaz/knowtis-app --skill deployinggit clone --depth 1 https://github.com/jovandyaz/knowtis-appWrote 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/jovandyaz/knowtis-app/deploying)<a href="https://agentmods.dev/skills/jovandyaz/knowtis-app/deploying"><img src="https://agentmods.dev/badge/skills/jovandyaz/knowtis-app/deploying.svg" alt="Measured on agentmods" 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 | $0.00103 | $0.01534 |
| Opus 5 | $0.00051 | $0.00767 |
| Sonnet 5 | $0.00021 | $0.00307 |
| Haiku 4.5 | $0.00010 | $0.00153 |
Grade A, and why
deploying 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnosing CI and deploying Knowtis
All deploy targets are CI-driven from GitHub Actions. Neither Vercel's nor Railway's Git integrations are active. Use references/ci-pipeline.md for affected checks and references/deployment.md for runtime topology and configuration.
Mental model
push to main → affected lint/typecheck/test/build + migration drift check
├─ notes affected → Vercel notes project
├─ backoffice affected → Vercel backoffice project
├─ api affected → railway-deploy.sh (waits for terminal status)
└─ mcp affected → railway-deploy.sh (if RAILWAY_MCP_SERVICE_ID is set)
The facts that resolve most deploy confusion
- Vercel never deploys directly from a push — Git deployments are disabled. Check the affected app and its corresponding
deploy-frontendordeploy-backofficejob. railway upuploads the snapshot, then Railway can skip its build viawatchPatterns. Explicitrailway up --ciexits 0 when build logs say “No changed files matched patterns”; a detached deployment may later becomeSKIPPED, observable by polling its exact ID. Compare that state with the Nx affected set and never report it as a successful deployment. The API patterns currently omitpackages/**, so package-only transitive changes require particular scrutiny.- Production migrations run in Railway's release phase. CI applies migrations only to its test database and separately checks generated migration drift.
- CLI return is not sufficient evidence in agent automation. A non-TTY invocation can return after upload, explicit
--cihas a watch-pattern early-success path, and--detachonly queues work. Userailway up --detach --json, capture that exact deployment ID, and poll it toSUCCESS; a healthy endpoint alone may still be the previous deployment. - Healthcheck gates differ by service: API uses
/api/v1/health/pingwith 120 seconds; MCP uses/healthwith 60 seconds. Check the matching service configuration when a build succeeds but never becomes live. - Manual escape hatch: direct Railway deploys bypass CI and are for explicit emergencies only. Prefer the repository's gated deploy script; otherwise use
railway up --detach --json, poll the returned deployment ID toSUCCESS, then verify the service health endpoint before reporting completion.
What ships with it
4 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.
- 3d ago First seen · 78 lines · 103 tokens per session scan A 1e79b3fa1a44
deploying is a skill published in the GitHub repository jovandyaz/knowtis-app (3 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 1,534 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…
collavre
Manage Collavre Creatives (hierarchical tasks/content blocks) via CLI. Use when creating, retrieving, updating, importing, or batch-operating on Creatives. Creatives are tree-structured items with automatic progress rollup — like a smart to-do list that doubles as a structured document.
escurel-platform
Use when building an application that consumes the Escurel knowledge-base service as its data store — designing a tenant's skill/instance data model, calling the agent tools…
writing-specs
Use when writing or editing a spec inside a Pairdown room — a document a team will read without you in the room. Covers where to think out loud versus what belongs in the document, and the rules that keep the document skimmable.
joining-a-room
Use when the user wants to join, open, create or leave a Pairdown room, when they mention a room id or a Pairdown link, when they ask what rooms exist, or when they ask why an agent is not showing up in a room. Covers attaching a session to a room, how being summoned works, and the two things that usually go wrong.
demo-video
Record Collavre demo / feature-intro videos from a declarative YAML scenario. Drives a local dev server with Playwright, animates the REAL AI streaming UI via a local fake OpenAI server, and post-processes to MP4 + poster per theme/size. Use when creating or updating product demo videos, feature walkthroughs, or…