Github Graphql API requests only cost 1 point when not paired with rateLimit

I see some strange behaviour with GitHub Graphql API. If you don’t query the rateLimit with a query, it only costs 1 point. but if you query rateLimit with a query it costs as it should. Has anyone seen this before?

how to reproduce on GitHub Explorer:
run this query:

{
  rateLimit {
    cost
    remaining
  }
  search(first: 100, type: ISSUE, query: "is:issue org:asyncapi is:open") {
    pageInfo {
      hasNextPage
      endCursor
    }
    nodes {
      ... on Issue {
        id
        title
        resourcePath
        repository {
          name
        }
        reactions(last: 1) {
          totalCount
        }
        comments(first: 100) {
          totalCount
          pageInfo {
            hasNextPage
          }
          nodes {
            reactions(last: 1) {
              totalCount
            }
          }
        }
      }
    }
  }
}

It shows your query costs 102 points which is understandable since it’s a complicated query.
Now note how many points are remaining and run the query WITHOUT the rateLimit as many times as you want:

{
  search(first: 100, type: ISSUE, query: "is:issue org:asyncapi is:open") {
    pageInfo {
      hasNextPage
      endCursor
    }
    nodes {
      ... on Issue {
        id
        title
        resourcePath
        repository {
          name
        }
        reactions(last: 1) {
          totalCount
        }
        comments(first: 100) {
          totalCount
          pageInfo {
            hasNextPage
          }
          nodes {
            reactions(last: 1) {
              totalCount
            }
          }
        }
      }
    }
  }
}

Now query how many points are remaining:

{
  rateLimit {
    remaining
  }
}

you can see it only costed 1 point for each request.