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 skills add Knuckles-Team/servicenow-api --skill servicenow-app-enginegit clone --depth 1 https://github.com/Knuckles-Team/servicenow-apiWrote 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/knuckles-team/servicenow-api/servicenow-app-engine)<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-app-engine"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-app-engine/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/knuckles-team/servicenow-api/servicenow-app-engine"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-app-engine.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.00179 | $0.01322 |
| Opus 5 | $0.00089 | $0.00661 |
| Sonnet 5 | $0.00036 | $0.00264 |
| Haiku 4.5 | $0.00018 | $0.00132 |
Grade A, and why
servicenow-app-engine 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 9d 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.
ServiceNow App Engine (scoped apps as metadata-as-code)
A scoped ServiceNow application is a namespaced bundle of metadata records (tables, rules,
ACLs, menus, catalog items…). App Engine Studio (AES) / Application Studio build that
bundle through a UI; this skill builds the same bundle as Fluent code and reconciles
the two views. It defers the build/deploy/test mechanics to servicenow-sdk-lifecycle.
When to use
- Designing a scoped app's shape: scope,
x_prefix,now.config.json, file layout. - Mapping an App Engine Studio artifact to the Fluent API that produces it.
- Assembling a coherent app from multiple artifacts (data model + logic + security + nav + request UX).
- Packaging/publishing a scoped app across instances.
When NOT to use
- CLI lifecycle mechanics (init/build/transform/deploy/ATF) →
servicenow-sdk-lifecycle. - Flow Designer flows/subflows/actions →
servicenow-workflow-studio. - Reading the raw samples →
servicenow-sdk-docs. - Ad-hoc live record CRUD →
servicenow-table-api.
Prerequisites
- A Fluent project (scaffold via
servicenow-sdk-lifecycle→references/project-init.md). - For packaging/publish: the
servicenow-apiMCP server via themcp-clientskill. Env + tag matrix:agent-tools/mcp-client/references/servicenow-api.md.
The mental model
Everything in a scoped app is a record in a sys_* table, namespaced to a scope.
Fluent constructs (Table, BusinessRule, Acl, ApplicationMenu, ServiceCatalog,
Record, …) are typed emitters for those records. "Build the app as code" = author those
constructs, then ship them via the SDK lifecycle.
Reference map — open just-in-time
references/scoped-app-anatomy.md—sys_scope, thex_<prefix>_namespace,now.config.json,package.json, and thesrc/fluent/layout. Read first when starting or structuring an app.references/app-engine-studio-concepts.md— what AES / Application Studio are, their artifact vocabulary (data tables, experiences, logic-and-automation, security), and how a code-first project coexists with them. Read when reconciling with the UI.references/metadata-as-code-mapping.md— the master table: App Studio artifact → Fluent API → canonicalservicenow-sdk-docssample. Read when you know what you want and need the construct + example.references/full-app-walkthrough.md— assemble a working app end-to-end (table + business rule + ACL + application menu + catalog item), cross-referencing the samples. Read when building a whole app rather than one artifact.references/packaging-and-publish.md— package and promote the scoped app across instances viaservicenow_cicd+servicenow_update_sets. Read at release time.
What ships with it
6 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.
- 9d ago First seen · 89 lines · 179 tokens per session scan A b998c3d198be
servicenow-app-engine is a skill published in the GitHub repository Knuckles-Team/servicenow-api (19 stars, last pushed 12d ago), licensed MIT. It adds 179 tokens to every session and 1,322 once invoked, about $0.0009 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-30.
Other skills, from other repositories
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…