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/jaipilot/jaipilot/jaipilot-maintainer-intentnpx skills add JAIPilot/jaipilot --skill jaipilot-maintainer-intentgit clone --depth 1 https://github.com/JAIPilot/jaipilotWrote 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/jaipilot/jaipilot/jaipilot-maintainer-intent)<a href="https://agentmods.dev/skills/jaipilot/jaipilot/jaipilot-maintainer-intent"><img src="https://agentmods.dev/badge/skills/jaipilot/jaipilot/jaipilot-maintainer-intent.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.1 | $0.00057 | $0.01563 |
| Opus 5 | $0.00028 | $0.00781 |
| Sonnet 5 | $0.00011 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
jaipilot-maintainer-intent 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 yesterday.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Establish maintainer intent before changing code
Treat repository history as part of the task specification. A technically correct patch is not a useful contribution when it duplicates active work, conflicts with an explicit roadmap, targets the wrong branch, or ignores the repository's established solution shape.
This is a read-only preflight. It does not authorize a comment, issue, branch, commit, push, or pull request. Preserve the worktree and unrelated user work: never switch branches, reset, clean, stash, or overwrite files while researching.
Establish the exact source
- Locate and read the complete repository guidance that applies before acting:
CONTRIBUTING.mdand linked contributor docs, applicable pull-request templates, repository instruction files, security, governance, developer, testing, and release guidance, and any AI-assisted contribution or disclosure policy. Check the root,.github/,docs/, and affected subtrees for scoped guidance; read the selected files completely. If a document is absent or inaccessible, report that fact instead of inventing a rule. - Record the repository, immutable revision, source issue or pull request, author, current state, target branch, head branch, and the user's intended delivery target. Distinguish a dependency bot branch from the default branch and from a human feature branch.
- For a pull request, read the complete conversation: title, body, commits, force-pushes, issue comments, reviews, inline review comments, check failures, linked issues, and linked pull requests. Do not infer the current decision from the title or final diff alone.
- Use only read access already available to the host. Do not expose credentials. Do not fetch or mutate refs merely to obtain history; ask before a read operation that would change local Git state. If relevant history is inaccessible, record that limitation and do not guess.
Use optional dependency-upgrade knowledge
If the user supplies or names CROSS_REPO_KNOWLEDGE.md, use it only for a dependency or version
upgrade. For unrelated maintenance, report it as out of scope and ignore it. Do not discover or load
the file unless the user explicitly names or supplies it. Match the exact coordinate, old and new
versions, bot type and head, failure signature, build system, runtime floor, and contribution
situation. Revalidate the source bot pull request, companion pull request, immutable revisions,
maintainer feedback, and current outcome. Treat Accepted records as precedent,
Maintainer-directed records as decision constraints, Candidate records only as diagnostic
hypotheses, and Unadopted records as warnings rather than solutions. Only independently verified
sources enter the evidence ranking below. Use matched records to choose the delivery channel and one
final decision, and report their identifiers plus any rejected or superseded approach.
What ships with it
2 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.
- yesterday Changed · +1 lines 450e30da7302
- 6d ago First seen · 120 lines · 57 tokens per session scan A a3396b0e7135
jaipilot-maintainer-intent is a skill published in the GitHub repository JAIPilot/jaipilot (6 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 1,563 once invoked, about $0.0003 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
spring-boot
Spring Boot 3.x development - REST APIs, JPA, Security, Testing, and Cloud-native patterns. Use for building enterprise Java applications with Spring Boot.
design-patterns
Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
java-coding-standards
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
azure-communication-common-java
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.