Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DataSQRL/sqrlnpx agentmods add skills/datasqrl/sqrl/configure-sqrlWrote 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/datasqrl/sqrl/configure-sqrl)<a href="https://agentmods.dev/skills/datasqrl/sqrl/configure-sqrl"><img src="https://agentmods.dev/badge/skills/datasqrl/sqrl/configure-sqrl/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/datasqrl/sqrl/configure-sqrl"><img src="https://agentmods.dev/badge/skills/datasqrl/sqrl/configure-sqrl.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.00069 | $0.05343 |
| Opus 5.5 | $0.00028 | $0.02137 |
| Sonnet 5.5 | $0.00014 | $0.01069 |
| Haiku 4.5 | $0.00007 | $0.00534 |
Grade A, and why
configure-sqrl 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 2d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update the configuration of a DataSQRL project by editing its *-package.json files or creating new ones. Read Configuration Files first (how the files are split and layered), then look up the key you need under Configuration Content.
The configuration supports environment placeholders in the configuration fields that process them. Read Environment Variables before adding credentials or tokens: the normal and secret forms have different compile-time behavior, and support is not universal across every configuration field.
Configuration Files
Base Config and Environment Overlays
For projects that need multiple deployment profiles, split configuration into a base (shared) and thin per-environment overlays to reduce duplication. This is a recommended project convention: SQRL accepts any ordered list of package JSON files and has no special meaning for the filenames or environment names.
<project>-shared-package.jsonis the base config file that includes common settings to every environment which could beversion,enabled-engines,script.main,script.api, and theengines/compilersettings.<project>-<env>-package.json(one per environment-test,-prod,-local,-dev) — add or overwrite ONLY what differs from the base configuration file (e.g.script.config.environment,test-runner, an engine override). Note that-devis a local development environment, like-local.
Example for the base config and environment overlays:
The lending360 project with a test and a production environment:
lending360-shared-package.json — the base: everything both environments share.
{
"version": "1",
"enabled-engines": ["flink", "postgres", "kafka", "vertx"],
"script": {
"main": "lending360.sqrl",
"api": {
"v1": {
"schema": "lending360-api/schema.v1.graphqls",
"operations": ["lending360-api/operations.v1.graphql"]
}
}
},
"engines": {
"flink": {
"config": {
"execution.runtime-mode": "STREAMING",
"table.exec.source.idle-timeout": "30 s"
}
}
},
"compiler": {
"api": { "protocols": ["GRAPHQL", "REST", "MCP"], "endpoints": "FULL" }
}
}
What ships with it
8 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.
- 2d ago Changed · +6 lines cef9be68e1b7
- 9d ago Changed 976f1d20c4ab
- 10d ago First seen · 365 lines · 69 tokens per session scan A d9a5fcf09b0b
configure-sqrl is a skill published in the GitHub repository DataSQRL/sqrl (230 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 5,343 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-30.
Other skills, from other repositories
adapter-aws-lambda
Deploy tRPC on AWS Lambda with awsLambdaRequestHandler() from @trpc/server/adapters/aws-lambda for API Gateway v1 (REST, APIGatewayProxyEvent) and v2 (HTTP, APIGatewayProxyEventV2), and Lambda Function URLs. Enable response streaming with awsLambdaStreamingRequestHandler() wrapped in awslambda.streamifyResponse().…
adapter-fetch
Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The endpoint option…
cloud-cli
Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.
interactive-login
Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
mirrord-db-branching
Helps users configure mirrord.json for database branching, enabling isolated database copies for safe development and testing. Use when the user wants to set up MySQL, MariaDB, PostgreSQL, MSSQL, MongoDB, Redis, DynamoDB, ClickHouse, Google Spanner, Amazon S3, turbopuffer, or generic branches, configure copy modes…
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…