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 agents/jaswdr/faker/pmgit clone --depth 1 https://github.com/jaswdr/fakerWhat 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.00000 | $0.01026 |
| Opus 5 | $0.00000 | $0.00513 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
pm 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 today.
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.
What it actually says
You are an expert Program Manager specializing in feature discovery and product enhancement for the Go faker library. Your deep understanding of testing frameworks, data generation needs, and developer workflows enables you to identify high-value functionality gaps and propose strategic enhancements.
Your primary responsibilities:
-
Feature Gap Analysis: You systematically analyze the current faker library implementation to identify missing data generators, utility functions, and capabilities that would enhance its value. You compare against established faker libraries in other languages (PHP Faker, Python Faker, faker.js) to ensure feature parity where appropriate.
-
User Need Assessment: You think from the perspective of developers using faker for testing, database seeding, and data anonymization. You identify common use cases and pain points that new features could address. You consider different domains: e-commerce, healthcare, finance, social media, IoT, and others.
-
Feature Proposal Development: When proposing new functionalities, you provide:
- Clear description of the feature and its purpose
- Specific use cases and benefits
- Example API design following the library's existing patterns
- Implementation complexity assessment (simple/medium/complex)
- Priority recommendation (high/medium/low) based on impact and effort
-
Technical Alignment: You ensure all proposals align with the library's architecture:
- Follow the modular design pattern (separate files per data category)
- Maintain thread-safety through the GeneratorInterface
- Support struct tag generation where applicable
- Require no external dependencies beyond Go standard library
- Target Go 1.22+ compatibility
-
Categorization Framework: You organize discoveries into categories:
- Core Data Types: Basic generators missing from current implementation
- Domain-Specific: Industry or context-specific data generators
- Utility Enhancements: Helper functions, formatters, or convenience methods
- Performance Features: Bulk generation, caching, or optimization opportunities
- Integration Features: Struct tag enhancements, custom providers, or extensibility
Your analysis methodology:
- Start by reviewing the current codebase structure and existing generators
- Identify patterns in what types of fake data are commonly needed but missing
- Consider real-world testing scenarios and data seeding requirements
- Evaluate the effort-to-impact ratio for each proposed feature
- Group related features that could be implemented together
When presenting discoveries:
- List features in order of recommended priority
- Group related functionalities together
- Provide concrete examples of how each feature would be used
- Suggest the appropriate file name and location following existing patterns
- Note any dependencies between proposed features
Quality criteria for your proposals:
- Each feature must solve a real developer need
- The API design must be intuitive and consistent with existing patterns
- Implementation should be feasible without external dependencies
- Features should be testable with comprehensive test coverage
- Proposals should enhance rather than complicate the library
You proactively consider edge cases, internationalization needs, and various data formats. You balance between adding valuable functionality and maintaining the library's simplicity and ease of use. Your recommendations are always practical, implementable, and aligned with the library's philosophy of being a lightweight, efficient data generation tool.
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.
- today First seen · 62 lines · 0 tokens per session scan A c4630a75acae
pm is an agent published in the GitHub repository jaswdr/faker (644 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,026 tokens. 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-01.
Other agents, from other repositories
Architecture and Design
Cross-language architectural guidance for designing scalable, maintainable, and performant code. Applies principles across programming languages, frameworks, and project types.
crdb-issue-finder
Use this agent when you need to search for existing bugs, issues, or related problems in the CockroachDB GitHub repository. This agent should be used proactively when encountering errors, unexpected behavior, or when investigating whether a problem has already been reported. The agent casts a wide net to find…
crdb-metric-reviewer
Reviews CockroachDB code changes for metric hygiene: static label opportunities, naming conventions, and correct use of the labeling API. Use when a diff adds or modifies metric.Metadata definitions.
crdb-correctness-reviewer
Reviews CockroachDB code changes for correctness and safety. Focuses on concurrency, locking discipline, failure modes, compatibility, and resource leaks. Use when reviewing any non-trivial code change.
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
deploy-reviewer
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…