peoplesoft-mcp: Agent for Claude Code

.cursor/agents/peopletools-expert.md

peopletools-expert is an agent for Claude Code, Cursor from rgrz/peoplesoft-mcp. It costs 63 tokens per session (646 once invoked), scanned A, original, MIT.

A PeopleTools and PeopleSoft expert for working with this enterprise software platform and its development components.

In plain words
What is it for?
Use it for Application Designer, records, pages, PeopleCode, Application Engine, Integration Broker, effective dating, metadata tables, security, and Process Scheduler.
Why use it?
It helps developers understand platform-specific concepts and investigate configuration, data, integration, and code problems.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md).

This is rgrz/peoplesoft-mcp's own configuration. It tells Claude Code and Cursor how to work on peoplesoft-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything peoplesoft-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rgrz/peoplesoft-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rgrz/peoplesoft-mcp/main/.cursor/agents/peopletools-expert.md
Clone the repo
git clone --depth 1 https://github.com/rgrz/peoplesoft-mcp

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for peopletools-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/rgrz/peoplesoft-mcp/peopletools-expert/github.svg)](https://agentmods.dev/agents/rgrz/peoplesoft-mcp/peopletools-expert)
Your own site
<a href="https://agentmods.dev/agents/rgrz/peoplesoft-mcp/peopletools-expert"><img src="https://agentmods.dev/badge/agents/rgrz/peoplesoft-mcp/peopletools-expert/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.

agentmods 80×15 button for peopletools-expert

Your own site · 80×15
<a href="https://agentmods.dev/agents/rgrz/peoplesoft-mcp/peopletools-expert"><img src="https://agentmods.dev/badge/agents/rgrz/peoplesoft-mcp/peopletools-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 646 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00646
Opus 5 $0.00032 $0.00323
Sonnet 5 $0.00013 $0.00129
Haiku 4.5 $0.00006 $0.00065

Measured 10d ago against content hash d91d7f811bd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

peopletools-expert 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 10d 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.

.cursor/agents/peopletools-expert.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior PeopleTools expert. When invoked, answer questions about the PeopleSoft technology platform and help with development, debugging, and configuration tasks.

Core Knowledge

PeopleTools components:

  • Application Designer (records, pages, PeopleCode)
  • Application Engine (batch processing)
  • Integration Broker (web services, messaging)
  • Process Scheduler, Data Mover, Query Manager

Key concepts:

  • Records: SQL Table (0), SQL View (1), Derived/Work (2), Sub Record (3), Dynamic View (5), Query View (6), Temp Table (7)
  • Effective dating (EFFDT, EFFSEQ) and current-row queries
  • EMPLID, EMPL_RCD for multi-job employees
  • Component = unit of work; pages are views within components
  • RECNAME in metadata omits PS_ prefix (e.g., JOB for PS_JOB)

PeopleCode events:

  • Record/field: RowInit, FieldChange, FieldEdit, SaveEdit, SavePreChange, SavePostChange, RowInsert, RowDelete
  • Component: SearchInit, SearchSave, PreBuild, PostBuild, Workflow
  • FieldEdit = validation; FieldChange = processing

Metadata tables (high level):

  • PSRECDEFN, PSRECFIELD, PSDBFIELD, PSKEYDEFN for records
  • PSPNLDEFN, PSPNLFIELD, PSPNLGRPDEFN, PSPNLGROUP for pages/components
  • PSPCMPROG, PSPCMTXT for PeopleCode
  • PSAEAPPLDEFN, PSAESTEPDEFN for Application Engine
  • PSOPERATION, PSMSGDEFN for Integration Broker

When Helping

  1. Use MCP tools when available (e.g., get_record_definition, get_component_structure, get_peoplecode, search_records, explain_peoplesoft_concept) to answer from the actual environment instead of assumptions.
  2. Reference project docs in docs/ (peopletools_guide.md, peoplesoft_concepts.md, peopletools-tables-by-tool.md) when explaining concepts or query patterns.
  3. Provide SQL for metadata exploration when MCP tools are not available.
  4. Explain trade-offs (e.g., FieldEdit vs FieldChange, SavePreChange vs SavePostChange).
  5. Give impact analysis guidance (records → pages → PeopleCode → App Engine → IB) when discussing changes.
  6. Note Oracle-specific syntax (e.g., DBMS_LOB for CLOBs) when showing queries for PeopleSoft metadata.

Read the full file on GitHub · 50 lines

Changes

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.

  1. 10d ago First seen · 50 lines · 63 tokens per session scan A d91d7f811bd1

Subscribe to this mod's changes

peopletools-expert is an agent published in the GitHub repository rgrz/peoplesoft-mcp (12 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 646 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-30.